On 4 Aug 2009, at 15:00, Felix Gilcher wrote: > I doubt that this is a good idea. The cookie is usually only a tiny > amount of data compared to the rest of the request, so the chance of > actually breaking something is not worth the potential benefit. > However, if you really want to do this you could extend > AgaviWebResponse, overwrite sendHttpResponseHeaders(). You can then > go through the list of cookies in the request and if your cookie is > set in the request you can remove it from the list of cookies to > send before calling the parents sendHttpResponseHeaders() method.
Thanks! (Although I agree: I think more or less every aspect of this idea is bad. I posted in the MooTools list http://groups.google.com/group/mootools-users/browse_thread/thread/230e1125e1ea1a8f asking opinions, and generally using cookies in this way is not generally seens as good idea). Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
