> 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.
I think David's idea was to have the proxy not forward the request to Apache+PHP until it was reasonably sure that erlang_receive() wouldn't block. It would know that the receive wouldn't block because Erlang told it so. It's a good idea even without the Erlang bit, I think. BTW, my implementation of erlang_receive() accepts an optional millisecond timeout. Which doesn't really solve this problem. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
