On 1/28/08, Itai Zukerman <[EMAIL PROTECTED]> wrote: > > > > Or you could use lift and Jetty and Comet so that your client's not > > polling, but has a persistent connection open to the server. > > Well, the point of this exercise is to leverage (!) all those PHP > people out there. It's probably easier to find people comfortable > with writing PHP front-ends than with lift/Scala, no? > > I'll grant, though, that Comet with Apache+PHP probably isn't going to > work.
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 > > -- lift, the secure, simple, powerful web framework http://liftweb.net Collaborative Task Management http://much4.us --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
