> > It probably won't work with Apache and PHP, but there may be a way to use > Nginx or something that can handle a lot more connections where there's a > 3-way interaction. Basically, the client connects to the server and > immediately calls Erlang and says, "send me a message when there's data > available for this session"... the session is suspended until there's data, > then it's allowed to flow through the PHP script. It's a bunch of plumbing > and a little bit of extra smarts on the Erlang side, but you get the > persistent connection. > > Another option may be to use Yaws as a proxy into Apache and do the same > thing (Yaws blocks the request until there's data and then forwards the > request to Apache.) > > I was a huge Apache fan (and still am for non-Comet sites). Unfortunately, > the set-up/tear-down costs for Apache are huge compared to lighttpd and > Nginx (and Jetty.) > > Thanks, > > David >
My guess is that the problem isn't that Apache isn't behind a proxy, but that the php script calls erlang_receive(), which causes it to block the OS thread. This doesn't scale to too many simultaneous clients. I think that unless you can make erlang_receive() not block the php OS thread (and I'm not sure that's possible) it will be hard to scale. Yariv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to "Bay Area Functional Programmers" To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/bayfp?hl=en -~----------~----~----~----~------~----~------~--~---
