<br><div class="gmail_quote">On Wed, Jun 18, 2008 at 12:59 PM, Ian Hickson <ian@hixie.ch> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Wed, 18 Jun 2008, Michael Carter wrote:<br>
><br>
> In that case I agree that the name shouldn't be TCPConnection. I propose<br>
> SocketConnection instead.<br>
<br>
</div>I was thinking WebSocket (with the protocol itself called the Web Socket<br>
Protocol or Web Socket Communication Protocol or some such).<br>
<div><div></div><div></div></div></blockquote><div><br>That sounds pretty good. Worth noting is that <a href="http://en.wikipedia.org/wiki/Internet_socket" target="_blank">http://en.wikipedia.org/wiki/Internet_socket</a> suggests that the term "Socket" doesn't refer to tcp/ip, rather it refers to multiple protocols. You can have a UDPSocket or an IPSocket just as easily as you could have a TCPSocket. In this context, neither WebSocket nor SocketConnection really present a naming problem.<br>
<br></div></div>-Michael Carter<br>