This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.w3.org/TR/websockets/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Is it really can be used like Winsocket? How can I use it? Posted from: 119.139.204.91 User agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
(In reply to comment #0) > > Comment: > Is it really can be used like Winsocket? How can I use it? > Hi, no this is not direct socket access (e.g. you cannot access port 993 on some computer and start to communicate with IMAP protocol). The name is confusing. WebSockets is protocol on its own. The link you posted is client side communication interface. The underlying communication protocol is here http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-17 (so far FF7 supports 7th version, Chrome supports 10th version, but will switch to 16th version) If you want to know more I suggest http://www.youtube.com/user/BronislavKlucka#p/c/3A7E9CAAA6B4CB73/0/2MSPwt3WGq8 video about mine server and client implementation and http://code.google.com/p/bauglir-websocket/ the implementation itself with some demos
The original request is a question and not a bug report. As such, I think this bug should be resolved as INVALID. Any objections to that?
(In reply to comment #2) > The original request is a question and not a bug report. As such, I think this > bug should be resolved as INVALID. Any objections to that? Not at all, this is no bug...