Hi,
I’m looking for guidelines as how to manage AirVantage data sessions for a long lived application.
The context is an FX30S application that daily send a data report to AV session at a fixed time. For that I actually used some timer and avdata API to request a data session, then release it.
My previous colleague used a different method that kept a session open at all time, which I figured was not optimal since we actually only send data like a few seconds a day.
But since I made the change to request session only as needed, the AirVantage timeline is much less readable since every heartbeat sends a whole registration + firmware/application state + de-registration, as before it only showd a registration update.
On another side, I see data session started/ended message in the timeline in a inconsistent way. For a while, it is synced accordingly to the heartbeat and/or the daily data session, but then when the device reboot or if a command is sent the session is seemingly kept open, but the messages from the heartbeat is still registration + firmware/application state + de-registration instead of registration update.
All of this is verry confusing, and the example I found only describe a short term 10 minute application lifetime, so not verry helpfull to this case.
Is there some guidelines, examples or recommandations as how to manage this ? Am I right to use this “request as needed only” way or is the good practice to keep the session alive as long as the application runs ?