On 2003.01.03, Peter M. Jansson <[EMAIL PROTECTED]> wrote: > Apparently in the latest version, nsvhr and nsunix work > out-of-the-box, although confirmation of this is sketchy.
Indeed, they should work out-of-the-box on 3.5.x, and I can personally attest to it, but nobody else has spoken up saying they're using it. Is anyone out there using nsvhr/nsunix out there? Anyone? > If you want to use the reverse-proxy approach, you're probably best > using TCP connections (it's not clear there are performance advantages > from using Unix domain sockets, as far as I know). As you said, the performance advantages aren't really big: if you do things right, you'll bind the virtual server's socket to localhost (your loopback interface) so opening/tearing down sockets isn't too terribly slow. The only advantage of running nsvhr with nsunix is that with nsunix we do FD passing, which gives the virtual server access to the actual client's socket -- which includes their peer address. Doing reverse-proxy with nssock, you only see the IP address of your reverse-proxy in your nslog ... with nsunix, you see the IP address of the actual requesting client. This is important to some people, me included. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
