On Wed, Jun 18, 2008 at 12:59 PM, Ian Hickson <[EMAIL PROTECTED]> wrote:
> On Wed, 18 Jun 2008, Michael Carter wrote: > > > > In that case I agree that the name shouldn't be TCPConnection. I propose > > SocketConnection instead. > > I was thinking WebSocket (with the protocol itself called the Web Socket > Protocol or Web Socket Communication Protocol or some such). > That sounds pretty good. Worth noting is that http://en.wikipedia.org/wiki/Internet_socket 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. -Michael Carter
