> 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.
For anyone interested -- PRG means ``POST-Redirect-GET''. It's the
common idiom of having the server reply to a POST with a redirect, which
causes the client to GET the next page, which in turn is cachable.
> Each and every POST request (XML) is huge... approx 2 - 5 kb.
As Phil Wadler once said about XML,
« The problem it solves is not hard. It doesn't solve it very well. »
Sorry, Arun, but I suspect that you're trying to solve a problem at the
wrong layer.
Juliusz
------------------------------------------------------------------------------
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
