E R schrieb am 16.04.2010 um 15:37:44 (-0500): [modperl and comet?] > I'm interested in adding a Comet capability to a (rather large) > mod-perl application. > > To get around XSS limitations, the Comet service will have the > same host and port as the web service. However, I don't want a > large mod-perl process tied up performing the Comet service. > > Is there a way that a web request can be passed off to another > process without tying up the Apache process? For instance, can > the Apache process pass the file descriptors for the HTTP > connection to another process which would free itself up for > handling the next Apache request?
I don't know how you could do that. Your mod_perl process could certainly send the response to a reverse proxy, but then it would be out of the business of servicing the request. > Is there another way to implement this? I'm rather clueless as to how to implement this myself, but it appears to me (maybe only due to limited knowledge) that unless you want to have one process tied up to servicing one client, you need non-blocking IO, like Danga::Socket (basically undocumented), or AnyEvent, and possibly other modules by Marc Lehmann. If anyone has ever done any such programming, I'd be curious how to get started, conceptually. -- Michael Ludwig