Closed thecosmicfrog closed 9 years ago
When opened, LaaG currently pokes the server for fresh times every 10 seconds (mobile) and 3 seconds (wearable). I can't think of any way to do this efficiently on the server side where the drawbacks won't outweigh the benefits. Closing.
Ideally, the stop forecast should reload as soon as new times are available on the server. One issue here is that LaaG uses its own API server which sits between the app and the Luas RTPI server. As such, the API server only updates when a HTTP request is made (e.g. from the LaaG app). I will be implementing memcached on the server-side to mitigate the load placed by a volley of HTTP requests, so I will look into how I can further improve things there.