From e0a935feeeffaf0083a8e4c3143a5ed48328d240 Mon Sep 17 00:00:00 2001 From: Unknown User Date: Tue, 8 Sep 2009 22:22:35 +0000 Subject: [PATCH] URL correction /psa git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3392 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0033.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0033.xml b/xep-0033.xml index ae0ffdb1..c6a30880 100644 --- a/xep-0033.xml +++ b/xep-0033.xml @@ -133,7 +133,7 @@

On the existing Jabber network, there are many opportunities to optimize stanza traffic. For example, clients that want to send the same stanza to multiple recipients currently must send multiple stanzas. Similarly, when a user comes online the server sends many nearly-identical presence stanzas to remote servers.

-

The 'http://jabber.org/protocol/address' specification provides a method for both clients and servers to send a single stanza and have it be delivered to multiple recipients, similar to that found in &rfc0822;. As a side-effect, it also provides all of the functionality specified by the old 'jabber:x:envelope' jabber:x:envelope - Message Envelope Information Extension proposal, which this XEP can supersede.

+

The 'http://jabber.org/protocol/address' specification provides a method for both clients and servers to send a single stanza and have it be delivered to multiple recipients, similar to that found in &rfc0822;. As a side-effect, it also provides all of the functionality specified by the old 'jabber:x:envelope' jabber:x:envelope - Message Envelope Information Extension proposal, which this XEP can supersede.

Support for Extended Stanza Addressing in a given server instance SHOULD be determined using &xep0030;. A conforming server MUST respond to disco#info requests.