Dear experts, My question is very trivial. Can APE be the solution that works around the problem of Apache's thread-per-request model if I use Apache as a web server, and APE server as my Comet server?
So far the only solution that I found for using Comet + Apache is to set up a Comet Server, and use a load balancer such as HAProxy to direct Comet requests to the Comet server hence avoiding Apache going nuts when there's too many concurrent requests. Virtual hosts and different domain names enable the two services (Comet + Web Server) to be on the same server. This is all because of Apache's thread-per-request model being a poor support for Comet requests. Even CometD has stated on their website that it is not a good idea to put Apache in front of a Bayeux server because of this. If I install APE on my server and use it properly =P will I have to worry about Apache's thread-per-request problem say if I implement a live chat system with Apache + APE ? I intend to build some live application on our existing site with APE, from many recommendations of using APE and what others have said, it seems like the answer to my question is yes, but I wanted to make sure of this. In fact, if the answer is yes, does anyone mind explaining to me how APE works around this problem with Apache? Please correct me if I've misunderstood anything, and sorry for this newbish question =P Thanks Wayne -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
