Hi all, How do you workaround the fact that, e.g., firefox doesn't invalidate a cached resource representation in the browser upon POSTing to the uri of the resource?
My scenario is this: A Google Map GETs a resource (a list of geo. points) which is cached for an hour on the client to avoid the overhead of additional HTTP requests. On another page a single point can be edited. Now POSTing an updated point to the list resource doesn't invalidate the cached representation as it should (a common problem: http://www.mnot.net/javascript/xmlhttprequest/cache.html). Since the cache is not invalidated the update is hidden on the map until time invalidates the cached representation. Any workarounds? kind regards Jakob
