Neil Schemenauer wrote:
On Fri, Jun 10, 2005 at 01:32:06PM -0500, Ian Bicking wrote:
I've had a few problems with SCGI 1.2. The attached patch:
* Fixes the connection retrying -- when addr wasn't reconstructed with
each retry, the second retry would always fail with Invalid Argument
error, not ECONNREFUSED.
The code worked on Linux. I suspect it did not work on many other
Unix systems. Thanks for pointing out the non-portability. I also
fixed the two mod_scgi modules. Note that you should call close()
on the existing socket before creating a new one.
Ah, right-o. I was testing on FreeBSD. It did seem like a peculiarly
prominent bug to be missed.
Another thing that would be nice for mod_scgi would be a different way
of configuring, more like FastCGI, that might look like:
SCGIMount /url 127.0.0.1:3000
That would indeed be nicer. Unfortunately, I don't have the time
and the Apache knowledge to make this happen.
I'm going out of town in a week, so I'll be busy for a while, but I'll
try to look at it. I looked at the Apache documentation, and it didn't
look too terribly hard -- it would be similar to how Alias works, and
there were several examples related to that.
Communication over named sockets would also be nice. I haven't really
used those before; maybe that's only a small change. With named sockets
you don't need to manage a registry of all the servers and ports on a
box, which would be helpful.
I don't see how named sockets are any better. You would have to
have a registry of paths instead of ports.
There's less than two bytes worth of ports, but hundreds of bytes of
paths to allocate. Much less chance of collision ;) Also, applications
are typically already named to manage configuration files and pid files
and whatnot; named sockets can use that same naming convention.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
_______________________________________________
Quixote-users mailing list
[email protected]
http://mail.mems-exchange.org/mailman/listinfo/quixote-users
