From 6f15ad8258d0ae73dbcec6c7d75bd5bf3b19689a Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 29 Sep 2008 22:25:30 +0000 Subject: [PATCH] 0.5 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2290 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0198.xml | 97 ++++++++++++++++++++++++++++------------------------ 1 file changed, 52 insertions(+), 45 deletions(-) diff --git a/xep-0198.xml b/xep-0198.xml index 8ab41710..26159e19 100644 --- a/xep-0198.xml +++ b/xep-0198.xml @@ -22,6 +22,12 @@ &infiniti; &hildjj; &stpeter; + + 0.5 + 2008-09-29 + psa +

Removed recommendation to use namespace prefixes; modified namespace to incorporate namespace versioning.

 + 0.4 2008-09-08 @@ -67,14 +73,14 @@ -

&xmppcore; defines the fundamental streaming XML technology used by XMPP (i.e., stream establishment and termination including authentication and encryption). However, the core XMPP specification does not provide tools for actively managing a "live" XML stream. In particular, the following management features might improve network reliability and the end-user experience (especially when connectivity is infrequent or power consumption is a key consideration):

+

&xmppcore; defines the fundamental streaming XML technology used by XMPP (i.e., stream establishment and termination including authentication and encryption). However, the core XMPP specification does not provide tools for actively managing a "live" XML stream. In particular, the following management features might improve network reliability and the end-user experience (especially when connectivity is infrequent):

  • Acknowledgements -- the ability to know if a particular stanza (or a series of stanzas) has in fact been received and processed by either of the endpoints.
    • -
  • Pings -- the ability to test the connectivity of the XML stream at any time.
    • +
  • Pings -- the ability to test the connectivity of the XML stream.
  • Resume -- the ability to quickly resume a stream that has been terminated.

Detailed descriptions of these features are provided in the remainder of this specification.

-

The facilities provided by this specification are different from those provided by &xep0079;, &xep0184;, and &xep0199;. The other specifications cover end-to-end and multi-hop acks and pings, which are useful in special scenarios, but unnecessary for checking of a single-hop stream. It is also expected that this protocol will revive interest in Advanced Message Processing (AMP), because single-hop acks are necessary for AMP delivery receipts to function properly.

+

The facilities provided by this specification are different from those provided by &xep0079;, &xep0184;, and &xep0199;. Those specifications cover end-to-end and multi-hop acks and pings, which are useful in special scenarios, but unnecessary for checking of a single-hop stream. It is also expected that this protocol will revive interest in Advanced Message Processing (AMP), because single-hop acks are necessary for AMP delivery receipts to function properly.

The basic concept behind stream management is that the initiating entity (either a client or a server) and the receiving entity (a server) can exchange commands for active management of the stream. In particular, instead of using XMPP IQ, message, or presence stanzas (which are relatively verbose), stream management uses a series of short XML elements at the root stream level.

The benefits to be gained from stream management include the following: