-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Component/s: 2nd or subsequent public review
-
Labels:None
-
Environment:
AMQP-BINDMAP
Submitted on Tuesday, May 3, 2016 - 17:14
Submitted by user:
Submitted values are:
Your name: Steve Huston
TC name: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings
(AMQP-BINDMAP)
TC email address: amqp-bindmap@lists.oasis-open.org
This ticket requests: Publish Committee Draft and release for public review
Title: Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB)
Version
1.0
Approval link:
https://www.oasis-open.org/apps/org/workgroup/amqp-bindmap/download.php/58073
Comment resolution log: http://
Abstract:
This specification describes how the WebSocket protocol can be used as a
transport for AMQP 1.0 protocol traffic. It is applicable for two main
scenarios:
● Firewall traversal. Since WebSocket connection establishment is
implemented
as standard HTTP traffic using the default ports (80 and 443), it is often
able
to pass through network security devices without requiring special
configuration
or opening of additional ports. When WebSocket is used as a transport for
AMQP
1.0 protocol traffic, this enables communication between arbitrary AMQP peers
such as an application using an AMQP client library and an AMQP message
broker,
separated by a firewall.
● Browser-based messaging. HTML5 compatible Web browsers have built-in
support
for the WebSocket protocol, thereby enabling a broad range of browser-based
AMQP
messaging scenarios.
Notification list:
users@qpid.apache.org
whatwg@whatwg.org
zolvarga@microsoft.com
Notes: Public review 1 yielded no comments from the public, so there's no
comment resolution log. There is a spreadsheet of resolved JIRAs handled
internally in the TC for this version.
The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN