On Monday, 24. March 2003 19:41, Chris Leishman wrote: > Matt, > > After the discussion last week, I've implemented patches against > AxKit to support caching of each stage of the processing. In the > process of implementing this, I had to make some pretty significant > changes to the way AxKit.pm handles requests. An upshot of this is > that there is now also support for TTL's of responses.
[...] Phew. Heavy stuff. I am happy someone tried that. Yet give us some time to digest that, try it out and everything. These changes are so deep, maybe they should be scheduled for AxKit 2.0, then possibly without backcompat-hacks... Anyhow. I'm eager to try it, maybe it will solve some of my problems I wanted to tackle for so long. Did you profile several scenarios? How is performance with this system? Doesn't it add too much overhead? Does "return 404;" from XSP still work? (which should go on processing, but send the final result with $r->status(404)) What about "throw Apache::AxKit::Exception::Retval(return_code => 403)"? (should abort immediately and just send the given error code). -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
