Oh, good point. It might be good to go with the optimizations only.
I'd just like to see a way to avoid what often happens... that is waiting one or two minutes before the connection is usable (that means I can both send and recieve). Pavel On Sat, 6 Sep 2008 01:08:42 +0100 Pedro Melo <[EMAIL PROTECTED]> wrote: > Hi, > > sorry about the previous empty email. Premature sending. > > On Sep 4, 2008, at 7:19 PM, Fabio Forno wrote: > > > On Thu, Sep 4, 2008 at 7:52 PM, Peter Saint-Andre > > <[EMAIL PROTECTED]> wrote: > >> Pavel Simerda wrote: > >>> > >>> +1 for a generic method > >> > >> Yeah, that means I need to re-work XEP-0237. :( > > > > Since Pavel has reminded XEP-59, what about transforming xep-237 > > into an extension of it? XEP-59 allows to set the boundaries of a > > result set by setting a first of last item; by extending the > > possible conditions (one is the sequence number, are there others?) > > the changes should be trivial. Instead of asking all the items > > after "last", request all the items after "sequence-no" > > <recent-than>sequence</recent-than> ? > > > > This is also the answer to the other question about what happens to > > large roster when there are stanza size limitations: just return a > > partial set and then ask the remaining ones. > > I read an email message from peter (ejabberd list I think) > mentioning that server-to-local-client flows where not restricted by > stanza limits. > > I remember because: > > a) I didn't knew that; > b) it makes sense after thinking about it; > c) I'm not sure which implementations do this. > > > > > > > -- > > Fabio Forno, Ph.D. > > Bluendo srl http://www.bluendo.com > > jabber id: [EMAIL PROTECTED] > -- Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
