Hey All, Proxied content and data pipelining is pretty much done in php-shindig, and the fetching & posting behind it works according to the normal http spec, get's are cached, post's are not. However data pipeling does mean all the requests to the app's back-end are posts, so not cached.
Has anyone looked at the possibility of caching those requests too (most likely strategy would probably be to use the request url + post body as cache key) for java shindig? I'm wondering if the trade-off of the resources it would cost would be worth it from the save-the-gadget-devs-server point of view. Any thoughts? -- Chris
