From a9aea086936e155cbb3c1cac24d49aa9a47aa15c Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 6 Apr 2009 03:39:23 +0000 Subject: [PATCH] typo git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2997 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0239.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0239.xml b/xep-0239.xml index c3495be4..16f5c789 100755 --- a/xep-0239.xml +++ b/xep-0239.xml @@ -74,7 +74,7 @@

This is an obvious improvement over the traditional representation.

It might be objected that the Binary XMPP representation requires a large number of XML elements. However, because all data is represented using only <zero/> and <one/>, the protocol can be significantly compressed using the standard ZLIB compression algorithm as defined in &rfc1950;, which SHOULD be enabled by default on the bxmpp port. Evidence from preliminary testing indicates that compression of Binary XMPP results in a representation less than 2% of the original size!

As a further simplification, Binary XMPP gets rid of the complicated stream negotiation process defined in RFC 3920. Instead, if a server supports Binary XMPP it advertises a special DNS SRV record _bxmpp._tcp in accordance with &rfc2782;. Furthermore, only one record is needed, thus saving precious port space. The RECOMMENDED port for Binary XMPP communication is 10110, but any port MAY be used.

-

To start a Binary XMPP stream, the sender simply connects via TCP at the advertised port and starts sending <zero/> and <one/> elements. The lack of a stream header simplifies XML parsing, introducing further performance improvemnets.

+

To start a Binary XMPP stream, the sender simply connects via TCP at the advertised port and starts sending <zero/> and <one/> elements. The lack of a stream header simplifies XML parsing, introducing further performance improvements.

The following examples showcase the tremendous efficiency of Binary XMPP using a complete session between a client and a server.