Hmm...good point. I guess I was concerned about a connection being initiated outside of the HTTP connection upgrade context, but maybe that's not a valid concern when using web sockets. I suppose something like socket.io is only accessible through HTTP and isn't sitting there with a port open like a server daemon would be.