A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
draft-murchison-jmap-websocket-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ken Murchison | ||
| Last updated | 2018-08-03 | ||
| Replaced by | draft-ietf-jmap-websocket | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-jmap-websocket | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines a binding for the JSON Meta Application Protocol (JMAP) over a WebSocket transport layer. A WebSocket binding for JMAP provides higher performance than the current HTTP binding for JMAP. Open Issues o Should we allow push notifications over the WS connection? o Should we allow out of order processing od requests?
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)