On 9-Aug-06, at 8:25 AM, [EMAIL PROTECTED] wrote:
This is quite on-topic I think. The answer is it's much faster.
There's a huge overhead in forking, and it just doesn't scale.
I presume that there is an event loop. When an event happens and
the processing of that event takes, for example, five minutes, what
happens when another event happens?
It's blocked until you re-enter the event loop. Obviously that's bad,
so I'll be investigating ways you can do long running stuff. It'll be
some API along the lines of:
$self->do_slow(sub { ... });
return CONTINUATION;
And when that's done (bearing in mind it'll be in a separate process
so you'll need to arrange for a way for data to be returned) the
continuation will pick up again at the next plugin in the chain.
(don't worry about the gritty details - I've done this sort of thing
for qpsmtpd already so it's just a SMOP and documenting it)
btw, how does one download axkit2?
I have a new app to write using ajax etc in about 3 weeks and
would like to use it if poss. Assuming the current paradigm for axkit2
is whats going to be decided upon of course.
At the moment it's SVN only. I can put a snapshot up somewhere if you
like.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
