fastcgi unix domain sockets or tcp
can anyone tell me why I should use a unix domain socket instead of a tcp socket on localhst for fastcgi? -- David Bear phone: 480-965-8257 fax: 480-965-9189 College of Public Programs/ASU Wilson Hall 232 Tempe, AZ 85287-0803 "Beware the IP portfolio, everyone will be suspect of trespassing"
David Bear wrote:
can anyone tell me why I should use a unix domain socket instead of a tcp socket on localhst for fastcgi?
I'd use Apache and proxypass instead... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Wed, 01 Sep 2004 19:57:46 -0700, David Bear <david.bear@asu.edu> wrote:
can anyone tell me why I should use a unix domain socket instead of a tcp socket on localhst for fastcgi?
The advantage of the tcp approach is that you can put a loadbalancer (e.g. pythondirector or pound) between your apache and your zope, giving you fail-over and load balancing. In theory you could write a load balancer that worked on a unix domain socket and read fastcgi requests, but I'm not aware of any that are already out there for this. Anthony
participants (3)
-
Anthony Baxter -
Chris Withers -
David Bear