Matches in DBpedia 2016-04 for { <http://wikidata.dbpedia.org/resource/Q859938> ?p ?o }
Showing triples 1 to 63 of
63
with 100 triples per page.
- Q859938 subject Q6378437.
- Q859938 subject Q6966079.
- Q859938 subject Q7348424.
- Q859938 subject Q7348550.
- Q859938 subject Q8635958.
- Q859938 abstract "WebSocket is a protocol providing full-duplex communication channels over a single TCP connection. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011, and the WebSocket API in Web IDL is being standardized by the W3C.WebSocket is designed to be implemented in web browsers and web servers, but it can be used by any client or server application. The WebSocket Protocol is an independent TCP-based protocol. Its only relationship to HTTP is that its handshake is interpreted by HTTP servers as an Upgrade request. The WebSocket protocol makes more interaction between a browser and a website possible, facilitating the real-time data transfer from and to the server. This is made possible by providing a standardized way for the server to send content to the browser without being solicited by the client, and allowing for messages to be passed back and forth while keeping the connection open. In this way a two-way (bi-directional) ongoing conversation can take place between a browser and the server. The communications are done over TCP port number 80, which is of benefit for those environments which block non-web Internet connections using a firewall. Similar two-way browser-server communications have been achieved in non-standardized ways using stopgap technologies such as Comet.The WebSocket protocol is currently supported in most major browsers including Google Chrome, Internet Explorer, Firefox, Safari and Opera. WebSocket also requires web applications on the server to support it.".
- Q859938 wikiPageExternalLink websockets.
- Q859938 wikiPageExternalLink charter.
- Q859938 wikiPageExternalLink websockets.
- Q859938 wikiPageExternalLink draft-hixie-thewebsocketprotocol-75.
- Q859938 wikiPageExternalLink draft-hixie-thewebsocketprotocol-76.
- Q859938 wikiPageExternalLink draft-ietf-hybi-thewebsocketprotocol.
- Q859938 wikiPageExternalLink draft-ietf-hybi-thewebsocketprotocol-00.
- Q859938 wikiPageExternalLink draft-ietf-hybi-thewebsocketprotocol-07.
- Q859938 wikiPageExternalLink draft-ietf-hybi-thewebsocketprotocol-10.
- Q859938 wikiPageExternalLink rfc6455.
- Q859938 wikiPageExternalLink www.websocket.org.
- Q859938 wikiPageWikiLink Q11189.
- Q859938 wikiPageWikiLink Q11288.
- Q859938 wikiPageWikiLink Q1192309.
- Q859938 wikiPageWikiLink Q12871890.
- Q859938 wikiPageWikiLink Q13414952.
- Q859938 wikiPageWikiLink Q13471026.
- Q859938 wikiPageWikiLink Q1351910.
- Q859938 wikiPageWikiLink Q1575.
- Q859938 wikiPageWikiLink Q165194.
- Q859938 wikiPageWikiLink Q165596.
- Q859938 wikiPageWikiLink Q183427.
- Q859938 wikiPageWikiLink Q206494.
- Q859938 wikiPageWikiLink Q217082.
- Q859938 wikiPageWikiLink Q220674.
- Q859938 wikiPageWikiLink Q254972.
- Q859938 wikiPageWikiLink Q2877351.
- Q859938 wikiPageWikiLink Q35773.
- Q859938 wikiPageWikiLink Q37033.
- Q859938 wikiPageWikiLink Q41242.
- Q859938 wikiPageWikiLink Q5155809.
- Q859938 wikiPageWikiLink Q544481.
- Q859938 wikiPageWikiLink Q548838.
- Q859938 wikiPageWikiLink Q5636136.
- Q859938 wikiPageWikiLink Q61694.
- Q859938 wikiPageWikiLink Q621530.
- Q859938 wikiPageWikiLink Q625306.
- Q859938 wikiPageWikiLink Q632343.
- Q859938 wikiPageWikiLink Q6368.
- Q859938 wikiPageWikiLink Q6378437.
- Q859938 wikiPageWikiLink Q6966079.
- Q859938 wikiPageWikiLink Q698.
- Q859938 wikiPageWikiLink Q726780.
- Q859938 wikiPageWikiLink Q7348424.
- Q859938 wikiPageWikiLink Q7348550.
- Q859938 wikiPageWikiLink Q739120.
- Q859938 wikiPageWikiLink Q7455583.
- Q859938 wikiPageWikiLink Q763744.
- Q859938 wikiPageWikiLink Q777.
- Q859938 wikiPageWikiLink Q7978451.
- Q859938 wikiPageWikiLink Q80998.
- Q859938 wikiPageWikiLink Q858321.
- Q859938 wikiPageWikiLink Q8635958.
- Q859938 wikiPageWikiLink Q8777.
- Q859938 wikiPageWikiLink Q8803.
- Q859938 comment "WebSocket is a protocol providing full-duplex communication channels over a single TCP connection. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011, and the WebSocket API in Web IDL is being standardized by the W3C.WebSocket is designed to be implemented in web browsers and web servers, but it can be used by any client or server application. The WebSocket Protocol is an independent TCP-based protocol.".
- Q859938 label "WebSocket".