Just a sidenote to the roster sequencing... There are clients (e.g. Gajim) that ask for vCard right now to show user avatars.
In future the usual flow might be that the client asks sequentially for various user information via some PubSub/PEP requests. IMO we should not forget this when designing protocols for optimization. We might want to unify roster-optimization with PEP/PubSub optimization. Pavel On Thu, 04 Sep 2008 08:30:58 -0600 Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > Fabio Forno wrote: > > On Wed, Sep 3, 2008 at 4:13 PM, Peter Saint-Andre > > <[EMAIL PROTECTED]> wrote: > > > >>> This would signal the client that the max stanza size is 65355 > >>> bytes, and the max allowed rate of stanzas per second is 10. > >> I like that. > >> > >> /psa > >> > > > > What happens to your roster in that case? ;) > > We need roster sequencing. And especially I do. :) So please provide > some feedback on XEP-0237. > > > Not only a joke. Some extensions like ibb can support any size > > limitations, but other stanzas like rosters, large data forms or pub > > sub events have no mechanisms for being split into several packets > > In current implementations (AFAIK), stanzas that you exchange > directly with your server (e.g., roster, vCard) are exempt from the > stanza size limits. But if you try to send a big stanza to someone > else, the limit is enforced. Among other things, this means that you > can upload a big vCard but if someone tries to retrieve it the > request will fail. > > /psa > -- Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
