Caching route configuration and detecting updates

[Gustav Just]

My application caches the configuration and route data for a particular agency (to be precise, I build a database from it). I'm looking for some mechanism to check/test when my locally cached data needs to be updated. I've seen older discussions from some years ago w/Nextbus suggesting that simply supporting the "Last-Modified" field in the HTTP response header would do the trick. But I see no evidence this has been implemented. Any recent insight here would be welcomed.

As an aside: Perhaps because the NextBus API is relatively straightforward, there is no longer much discussion here? Or have nextbus api discussions in effect moved to another forum (if so which?). There does not seem to be an obvious way to contact NextBus directly regarding technical questions (and I can imagine supporting the public feeds could become a nightmare).

[Guillaume Campagna]

Re your aside, I think NextBus is basically dead. They still have active contacts but bugs on their side has been there for years and they don’t seems reactive (even with their client agencies from what I can tell.

On Jan 8, 2020, 16:42 -0500, Gustav Just <justbei...@gmail.com>, wrote:

My application caches the configuration and route data for a particular agency (to be precise, I build a database from it). I'm looking for some mechanism to check/test when my locally cached data needs to be updated. I've seen older discussions from some years ago w/Nextbus suggesting that simply supporting the "Last-Modified" field in the HTTP response header would do the trick. But I see no evidence this has been implemented. Any recent insight here would be welcomed.

As an aside: Perhaps because the NextBus API is relatively straightforward, there is no longer much discussion here? Or have nextbus api discussions in effect moved to another forum (if so which?). There does not seem to be an obvious way to contact NextBus directly regarding technical questions (and I can imagine supporting the public feeds could become a nightmare).

--
You received this message because you are subscribed to the Google Groups "NextBus API Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nextbus-api-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nextbus-api-discuss/c886cc24-b7ba-410a-b08f-b331dcfb44ef%40googlegroups.com.