Re: xinetd vs php socket server

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 28, 2011 at 3:34 PM, Bostjan Skufca <bostjan@xxxxxx> wrote:

> If you need high performance you probably already know that it will be very
> expensive CPU wise if workers are spawned on each request. If you don't, I
> would not bother with daemon and just use xinetd. You can always add
> daemon-handling stuff later on.
>
> Well I do hope you find a good working solution with as little
> inconvenience as possible,
> b.


hmm, wouldn't both the solutions most likely be forking?  php daemon would
fork since threading isn't supported, and xinetd, probly best to have it
fork for the same reason apache is typically configured to fork.  right?

-nathan

[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux