Re: xinetd vs php socket server
| From: | Nathan Nobbe | Date: | Mon, 28 Mar 2011 22:34:32 +0000 |
| Subject: | Re: xinetd vs php socket server | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-312108@lists.php.net to get a copy of this message | ||
On Mon, Mar 28, 2011 at 3:34 PM, Bostjan Skufca <bostjan@a2o.si> 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