On 8 Aug 2006 at 12:43, Also Sprach Matt Sergeant:

> On 8-Aug-06, at 12:19 PM, [EMAIL PROTECTED] wrote:
 
> > Is Danga::Socket  faster than opening a fifo pipe for reading and
> > immediately  forking when something is read, given that the
> > processing is fairly long winded after the read?
> 
> 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? I would imagine it gets 
processed straight away,but I have no idea how, what's the 
mechanism? threads? Or are multiple server daemons set up and 
the request passed to them, like apache does?

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.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to