Yeah...XEP-0059 seems to be that what i searched... :)<br><br><div><span class="gmail_quote">On 10/11/06, <b class="gmail_sendername">Jean-Louis Seguineau</b> <<a href="mailto:jean-louis.seguineau@laposte.net">jean-louis.seguineau@laposte.net
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Tobias,<br><br>I believe it would be a perfect use of XEP-0059 Result Set Management. And
<br>that would bode well with the XMPP approach of letting server do the hard<br>work. In addition, it would not break existing client or server<br>implementations.<br><br>Jean-Louis<br><br>-----Original Message-----<br>Message: 2
<br>Date: Wed, 11 Oct 2006 15:29:03 +0200<br>From: "Tobias Markmann" <<a href="mailto:tmarkmann@googlemail.com">tmarkmann@googlemail.com</a>><br>Subject: [jdev] Service Discovery (XEP-0030) and large item sets
<br>To: "Jabber software development list" <<a href="mailto:jdev@jabber.org">jdev@jabber.org</a>><br>Message-ID:<br> <<a href="mailto:5cfc0a8e0610110629o537a89e1v8cbc1786ff762e47@mail.gmail.com">
5cfc0a8e0610110629o537a89e1v8cbc1786ff762e47@mail.gmail.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi,<br><br>Given the following query stanza:<br><br><iq id='75'<br>> to='<a href="http://conference.jabber.org">
conference.jabber.org</a>'<br>> type='get'<br>> xml:lang='de-DE'><br>> <query xmlns='<a href="http://jabber.org/protocol/disco#items'/">http://jabber.org/protocol/disco#items'/</a>><br>> </iq>
<br><br><br>The server responds to this stanza with a large stanza, with hundreds of<br>items. If XMPP gets more common MUCs will have a lot more rooms. So why<br>don't split large stanzas in smaller chunks. Like in the following example:
<br><br><iq from='<a href="http://conference.jabber.org">conference.jabber.org</a>'<br>> to='<a href="http://tobiasfar@jabber.org/home">tobiasfar@jabber.org/home</a>'<br>> id='75'<br>> type='result'
<br>> part='1'<br>> part-count='2'><br>> <query xmlns='<a href="http://jabber.org/protocol/disco#items'">http://jabber.org/protocol/disco#items'</a>><br>> <item jid='<a href="mailto:comitedesabios@conference.jabber.org">
comitedesabios@conference.jabber.org</a>'<br>> name='comitedesabios (0)'/><br>> <item jid='<a href="mailto:asilo@conference.jabber.org">asilo@conference.jabber.org</a>'<br>> name='asilo (0)'/>
<br>> <item jid='<a href="mailto:blondie@conference.jabber.org">blondie@conference.jabber.org</a>'<br>> name='blondie (1)'/><br>> <item jid='<a href="mailto:esperanto@conference.jabber.org">esperanto@conference.jabber.org
</a>'<br>> name='Babilu esperante (4)'/><br>> <item jid='<a href="mailto:hawaii@conference.jabber.org">hawaii@conference.jabber.org</a>'<br>> name='Hawaii (0)'/><br>> </query><br>> </iq>
<br>><br>> <iq from='<a href="http://conference.jabber.org">conference.jabber.org</a>'<br>> to='<a href="http://tobiasfar@jabber.org/home">tobiasfar@jabber.org/home</a>'<br>> id='75'<br>> type='result'
<br>> part='2'<br>> part-count='2'><br>> <query xmlns='<a href="http://jabber.org/protocol/disco#items'">http://jabber.org/protocol/disco#items'</a>><br>> <item jid='<a href="mailto:kanava@conference.jabber.org">
kanava@conference.jabber.org</a>'<br>> name='kanava (0)'/><br>> <item jid='<a href="mailto:profit@conference.jabber.org">profit@conference.jabber.org</a>'<br>> name='Profit (3)'/><br>> <item jid='!use@
<a href="http://conference.jabber.org">conference.jabber.org</a>'<br>> name='!use (0)'/><br>> <item jid='<a href="mailto:directnet@conference.jabber.org">directnet@conference.jabber.org</a>'<br>> name='Directnet (1)'/>
<br>> <item jid='<a href="mailto:stevegt-ctl@conference.jabber.org">stevegt-ctl@conference.jabber.org</a>'<br>> name='stevegt-ctl (1)'/><br>> <item jid='<a href="mailto:asplinux@conference.jabber.org">
asplinux@conference.jabber.org</a>'<br>> name='asplinux'/><br>> <item jid='<a href="mailto:international@conference.jabber.org">international@conference.jabber.org</a>'<br>> name='international (0)'/>
<br>> </query><br>> </iq><br><br><br><br>This will result in some advantages like:<br><br> - smaller XML stanza sizes -> easier to handle for servers<br> - better responsiveness because you can still retrieve presences or
<br> other messages while receiving a large stanza<br><br>If someone knows a better way to do something like this, please tell me<br>about it.<br><br>regards<br>Tobias<br><br><br></blockquote></div><br>