Additionally, you will be limited to the number of forked Apache
processes.

Careful there, aren't we talking about forked Apache threads handling socket I/O? Why not set that limit has high as the number of persistent connections you might want to support simultaneously?

While it is no guarantee, most servers that handle WS will not limit you like that ...

I've never seen any socket server that didn't have a limit on the number of concurrent connections, using some sort of configuration directive.

instead, connecting to some kind of queue,



An Apache thread can connect to a queue too.

I built a setup last week using ActiveMQ, JMS and Stomp over
websockets connecting to PHP over FastCGI.  You are able to
send data over WS whenever you like.


Sorry, I don't understand that. Are you saying that a server process initiates I/O with a Web Socket client? I don't think that's possible.

-Nathan.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.