Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Charter for the [<a href="https://datatracker.ietf.org/wg/hybi/charter/" rel="nofollow">working group</a>] working group tasked with websockets, BiDirectional or Server-Initiated HTTP (hybi):</p> <blockquote> <p><strong>Description of Working Group</strong></p> <p>HTTP has most often been used as a request/response protocol, leading to clients polling for new data, or users hitting the refresh button in their browsers. Recent web applications are finding ways to communicate with web servers in realtime, pushing data from the server-side to the client as soon as it is available. However, these applications at present can only use a variety of HTTP mechanisms (e.g. long polling requests) to communicate with web servers bidirectionally.</p> <p>The Hypertext-Bidirectional (HyBi) working group will seek standardization of one approach to maintain bidirectional communications between the HTTP client, server and intermediate entities, which will provide more efficiency compared to the current use of hanging requests.</p> </blockquote> <p>HTTP still has a role to play; it's a flexible message oriented system. websockets was developed to provide bidirectionality and avoid the long polling issue altogether. [<a href="http://hacks.mozilla.org/2010/04/websockets-in-firefox/" rel="nofollow">it does this well</a>]. but it's simpler than http. and there's a lot of things that are useful about http. there will certainly be continued progress enriching http's bidirectional communication, be it comet or other push technologies. my own humble attempt is [<a href="http://github.com/rektide/pipe-layerBlockquote" rel="nofollow">http://github.com/rektide/pipe-layer</a>].</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload