My personal choice of sockets is based on: 1. They're mildly faster because there's no TCP/IP connection overhead. 2. I know where they are. I keep the PID and SOCK in for my django applications with the applications. Makes debug, manually restarting, etc very nice and clean. 3. I don't have to pull a port number out of thin air (and hope it won't clash) every time I make a new interpreter.
On the server that I was experiencing this with, I actually moved to nginx (don't worry, I still have two servers with Cherokee; I'm still allowed to post in here ;) and that solved my issue immediately as well as teaching me to love config files more than I love Cherokee's admin (I'm going to start a new thread on this in a second). But sockets should work as well as tcp. If it doesn't, there's a problem with the socket IO implementation.
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
