I'm working on an app that reads changing job data from a web service.
This should be up-to-date, within a few seconds to a minute of any change occurring.
Normally I might go straight for regular polling at the client, but...
1. There may be many clients connected to the server - add them together and there is a fair load (on the server), even if only checking to see if the data has changed.
2. In addition, I read that polling is frowned upon for battery devices, because of the load on the battery (?)
Ok, so a 'push' application will help here, I read; the HTTP connection is kept alive, and the server signals the *client* when new data needs to be sent.
Can we do this in B4a? If so, how?
In particular how is the HTTP connection managed?
Anyone have any experiences?
TIA
Steve
This should be up-to-date, within a few seconds to a minute of any change occurring.
Normally I might go straight for regular polling at the client, but...
1. There may be many clients connected to the server - add them together and there is a fair load (on the server), even if only checking to see if the data has changed.
2. In addition, I read that polling is frowned upon for battery devices, because of the load on the battery (?)
Ok, so a 'push' application will help here, I read; the HTTP connection is kept alive, and the server signals the *client* when new data needs to be sent.
Can we do this in B4a? If so, how?
In particular how is the HTTP connection managed?
Anyone have any experiences?
TIA
Steve