QQP - Quick Queues Protocol
draft-bollow-qqp-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Norbert Bollow | ||
| Last updated | 2006-05-08 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-bollow-qqp-02.txt
Abstract
The QQP protocol specifies a method for transmitting multiple webservice requests and responses between two Hosts. QQP plays the role of transport protocol for the QRPC webservice protocol, similar to how XML-RPC and SOAP often use HTTP over TCP as transport protocol. QQP is called the "Quick Queues Protocol" because it is faster than transmitting XML data via HTTP over TCP for several reasons. QQP is also designed to handle Internet Protocol multihoming, hiding IP address changes from application layer software without need for introducing an additional protocol layer for that purpose.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)