On Monday, March 24, 2003, at 11:51 PM, J�rg Walter wrote:
On Monday, 24. March 2003 22:25, Chris Leishman wrote:The changes are reasonably deep - but it's mostly contained within the AxKit.pm module and everything else is pretty backwards compatible (with the exception of the Cache API - of which I can't find any derived classes anyway).
I know of one... though not yet widely available.
Ok. Well, that will be a small but certainly not insurmountable problem. And I really think that the API needs to be changed to do this effectively. However, the changes to the API are quite minimal - mostly just in the way the deliver function is called.
<snip>
Can you do real timings? Requests/second using 'ab' or something?
Also, XSP-after-XSLT is uncommon, and commonly a design error, so this is not
a big gain (except for my round-tripping-XML solution which does just that).
I'd love to see real numbers.
To be honest, I don't really have the set-up to do it right now. I'm currently doing the dev on my laptop whilst I travel around - and its probably not the best reference platform ;-) However, in my tests I certainly didn't notice any real slowdown. If I do get some status, I'll let you know.
<snip>
I haven't really checked that - but I see no reason why it wouldn't.
The status method wasn't proxied by AxKit::Apache, so it should work as
normal. It seems kind of ugly doing that though, since you can't be
sure what else is down the pipeline.
AxKit.pm had explicit support for that, saving any nonzero return code to set
it later as $r->status. The place is quite easy to spot.
Ok. I think I know what you mean. If the handler returns any non-OK code, it is later set as $r->custom_handler($code, $result). This should work as normal. I'm quite sure there's no fiddling with $r->status though.
$ grep status lib/AxKit.pm $
Please, have a play with it and see if you can find any problems.Sure. Whenever I get my shiny new 48h day, I will do ;-)
Yeah...I wish I could have that too sometimes.
Regards, Chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
