Hi Juliusz, Thanks for your response.
Yes, I understand that POST, by definition is non-cacheable. I also have PRG pattern in mind. With PRG pattern, caching the GET part is simpler. However, sending the first POST request to the server could not be avoided. There is a reason for why I am very specific about not sending even the POST request to the server. Each and every POST request (XML) is huge... approx 2 - 5 kb. Also I am very sure about the consistency of response to these POST requests. They are idempotent. Well.. so far I successfully managed to get POST caching work with Polipo (however with some glitches with event polling/scheduling). Also gotta test it extensively before coming to a conclusion. Currently working on to get the glitches resolved. Polipo is fantastic. Well structured and nicely designed to understand what it does. Anyway, thanks once again for your pointers. Regards, Arun S. On 25/04/2009, Juliusz Chroboczek <[email protected]> wrote: > Dear Arun, > >> There are some specific requests that are known to be idempotent and those >> requests are to cached. > > Are you sure that you don't want to change the protocol to use GET > instead of POST? POST, by definition, is not cachable. > >> It would be very helpful if someone throws a light on this. > > Sorry, but I think it's a horrible idea. > > Juliusz > -- Regards, Arun S. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Polipo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/polipo-users
