moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 10:12:19 -05:00
Code Issues Releases Wiki Activity

typo

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2997 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-04-06 03:39:23 +00:00
parent f705ccf7a4
commit a9aea08693
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
xep-0239.xml
View File

@ -74,7 +74,7 @@
<p>This is an obvious improvement over the traditional representation.</p> <p>This is an obvious improvement over the traditional representation.</p>
<p>It might be objected that the Binary XMPP representation requires a large number of XML elements. However, because all data is represented using only &lt;zero/&gt; and &lt;one/&gt;, 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!</p> <p>It might be objected that the Binary XMPP representation requires a large number of XML elements. However, because all data is represented using only &lt;zero/&gt; and &lt;one/&gt;, 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!</p>
<p>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.</p> <p>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.</p>
<p>To start a Binary XMPP stream, the sender simply connects via TCP at the advertised port and starts sending &lt;zero/&gt; and &lt;one/&gt; elements. The lack of a stream header simplifies XML parsing, introducing further performance improvemnets.</p> <p>To start a Binary XMPP stream, the sender simply connects via TCP at the advertised port and starts sending &lt;zero/&gt; and &lt;one/&gt; elements. The lack of a stream header simplifies XML parsing, introducing further performance improvements.</p>
</section1> </section1>
<section1 topic='Examples' anchor='examples'> <section1 topic='Examples' anchor='examples'>
<p>The following examples showcase the tremendous efficiency of Binary XMPP using a complete session between a client and a server.</p> <p>The following examples showcase the tremendous efficiency of Binary XMPP using a complete session between a client and a server.</p>