On Wed, Oct 12, 2011 at 12:40 PM, Andrew McNabb <[email protected]> wrote:
> I'm not a Web Sockets expert, but this isn't how I understand things. > As far as I can tell, a Web Socket is just a normal outbound connection > on port 80. It would help if ports other than 80 are blocked for > outgoing connections, but it wouldn't do anything fancy. > Sorry I didn't write that very clearly. I mean that without sockets, if you wanted to push data to another machine, it would have to have an open port and be listening on the port for the information. In this case, you can tell the browser to open a socket over port 80 and listen for the information (as I understand it). I mean that you can overcome the need to open ports for incoming connections. I was trying to point out that the real advantage is not that it allows you to bypass closed ports other than 80. -John -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
