217
edits
Difference between revisions of "Tech pages/BOSH"
Jump to navigation
Jump to search
m
no edit summary
(initial copy) |
Neustradamus (talk | contribs) m |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
BOSH is "Bidirectional-streams Over Synchronous HTTP", a technology for two-way communication over the Hypertext Transfer Protocol (HTTP). BOSH emulates many of the transport primitives that are familiar from the Transmission Control Protocol (TCP). For applications that require both "push" and "pull" communications, BOSH is significantly more bandwidth-efficient and responsive than most other bidirectional HTTP-based transport protocols and the techniques known as AJAX. BOSH achieves this efficiency and low latency by avoiding HTTP polling, yet it does so without resorting to chunked HTTP responses as is done in the technique known as Comet. To date, BOSH has been used mainly as a transport for traffic exchanged between Jabber/XMPP clients and servers (e.g., to facilitate connections from web clients and from mobile clients on intermittent networks). However, BOSH is not tied solely to XMPP and can be used for other kinds of traffic, as well. | BOSH is "Bidirectional-streams Over Synchronous HTTP", a technology for two-way communication over the Hypertext Transfer Protocol (HTTP). BOSH emulates many of the transport primitives that are familiar from the Transmission Control Protocol (TCP). For applications that require both "push" and "pull" communications, BOSH is significantly more bandwidth-efficient and responsive than most other bidirectional HTTP-based transport protocols and the techniques known as AJAX. BOSH achieves this efficiency and low latency by avoiding HTTP polling, yet it does so without resorting to chunked HTTP responses as is done in the technique known as Comet. To date, BOSH has been used mainly as a transport for traffic exchanged between Jabber/XMPP clients and servers (e.g., to facilitate connections from web clients and from mobile clients on intermittent networks). However, BOSH is not tied solely to XMPP and can be used for other kinds of traffic, as well. | ||
== Specifications == | == Specifications == | ||
BOSH is defined in two specifications: | BOSH is defined in two specifications: | ||
* XEP-0124: Bidirectional-streams Over Synchronous HTTP | * [http://xmpp.org/extensions/xep-0124.html XEP-0124: Bidirectional-streams Over Synchronous HTTP (BOSH)] | ||
* XEP-0206: XMPP Over BOSH | * [http://xmpp.org/extensions/xep-0206.html XEP-0206: XMPP Over BOSH] | ||
== Implementations == | == Implementations == | ||
=== Servers === | === Servers === | ||
The following XMPP servers include built-in support for BOSH: | The following XMPP servers include built-in support for BOSH: | ||
* ejabberd | * ejabberd | ||
| Line 21: | Line 17: | ||
=== Connection Managers === | === Connection Managers === | ||
The following standalone XMPP connection managers can be used with a wide variety of XMPP servers: | The following standalone XMPP connection managers can be used with a wide variety of XMPP servers: | ||
* Araneo | * Araneo | ||
| Line 29: | Line 24: | ||
=== Clients === | === Clients === | ||
* Adium | * Adium | ||
* Gajim | * Gajim | ||
| Line 40: | Line 34: | ||
=== Libraries === | === Libraries === | ||
* emite (gwt) | * emite (gwt) | ||
* gloox (C++) | * gloox (C++) | ||
| Line 51: | Line 44: | ||
== Discussion Venues == | == Discussion Venues == | ||
The XMPP Standards Foundation maintains a dedicated email list ([http://mail.jabber.org/mailman/listinfo/bosh bosh@xmpp.org]) about BOSH, intended as a low-volume venue for discussion of BOSH implementation and protocol issues. As with all XSF technology lists, the bosh@xmpp.org list is open to all interested individuals. | |||
The XMPP Standards Foundation maintains a dedicated email list ( | |||
* Info page and subscription information | * Info page and subscription information | ||
* Subscribe via email | * Subscribe via email | ||
* Discussion archives | * Discussion archives | ||