1 The above link is relevant for Apache 1.3. For Apache2, the link is dominia.org/djao/limitipconn2.html. Anyways I will try it. – Mohit Nanda Jan 16 '09 at 15:20.
I'm not sure if it will useful to you but definitely worth a chance. Maybe you can use the directives MaxClients and ListenBackLog Although they apply to the concurrent access to the entire server, not only your application, and on a resource base.
We completely built an application layer thing that stored, checked and restricted the limit on # of application users that could be logged on concurrently. If it got exceeded, we sent them to a 'waiting room' - worked like a charm. So it was all application managed - we had multiple apache servers in a cluster.
We were not using the Zend clustering stuff , IMO.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.