No subject
Fri Aug 3 19:33:07 CDT 2007
so ... and if my j2me client drops connection to the xmpp server, just
reconnect, authenticate, send my presence, without requestiong roster. I
believe this would fasten up things a lot and make the auth / post-auth
process much lighter. .
What do you think ? Am I missing something else here ?
Thanks again for helping.
Cheers
Alex
On Tue, May 6, 2008 at 12:31 AM, Fabio Forno <fabio.forno at gmail.com> wrote:
> On Mon, May 5, 2008 at 4:53 PM, az lists <azlist1 at gmail.com> wrote:
>
> > I've been googling a litle and it seems that this issue has been
> discussed
> > during one of the xmpp guru's meeting in Brussels earlier this year. A
> > proposed solution was to implement a fast reconnect mechanism.
> > I wanted to know what was the evolution on this side of the standards
> > definition.
>
> Basically stalled. However a standard is just a first step, then you
> have to wait for server support, and time will pass. The only working
> solution for these things now is a BOSH connection manager that keeps
> the session alive also when disconnected.
>
> As far as I know roster retrieval is mandatory for a resource if
> > it wants to be notified of new presence messages "If an available
> resource
> > does not request the roster during a session, the server MUST NOT send
> it
> > presence subscriptions and associated roster updates." The problem here
> is
> > that I need the client to receive roster and presence updates even if
> the
> > roster wasn't requested after re-authenticating to the xmpp server.
>
> It's about presence subscriptions, not general presence. If you don't
> download the roster you are implicitly saying that you don't want to
> handle it, so any update is filtered out.
> Instead you are still able to receive presence, just send your own first.
>
> --
> Fabio Forno, Ph.D.
> Bluendo srl http://www.bluendo.com
> jabber id: ff at jabber.bluendo.com
>
------=_Part_25692_32597211.1210033774773
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Thank you Fabio for your answer. <br>From your answer I guess I could donwload the roster once every X hours or so ... and if my j2me client drops connection to the xmpp server, just reconnect, authenticate, send my presence, without requestiong roster. I believe this would fasten up things a lot and make the auth / post-auth process much lighter. . <br>
<br>What do you think ? Am I missing something else here ? <br><br>Thanks again for helping. <br><br>Cheers <br><br>Alex<br><br><div class="gmail_quote">On Tue, May 6, 2008 at 12:31 AM, Fabio Forno <<a href="mailto:fabio.forno at gmail.com">fabio.forno at gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Mon, May 5, 2008 at 4:53 PM, az lists <<a href="mailto:azlist1 at gmail.com">azlist1 at gmail.com</a>> wrote:<br>
<br>
> I've been googling a litle and it seems that this issue has been discussed<br>
> during one of the xmpp guru's meeting in Brussels earlier this year. A<br>
> proposed solution was to implement a fast reconnect mechanism.<br>
> I wanted to know what was the evolution on this side of the standards<br>
> definition.<br>
<br>
</div>Basically stalled. However a standard is just a first step, then you<br>
have to wait for server support, and time will pass. The only working<br>
solution for these things now is a BOSH connection manager that keeps<br>
the session alive also when disconnected.<br>
<div class="Ih2E3d"><br>
As far as I know roster retrieval is mandatory for a resource if<br>
> it wants to be notified of new presence messages "If an available resource<br>
> does not request the roster during a session, the server MUST NOT send it<br>
> presence subscriptions and associated roster updates." The problem here is<br>
> that I need the client to receive roster and presence updates even if the<br>
> roster wasn't requested after re-authenticating to the xmpp server.<br>
<br>
</div>It's about presence subscriptions, not general presence. If you don't<br>
download the roster you are implicitly saying that you don't want to<br>
handle it, so any update is filtered out.<br>
Instead you are still able to receive presence, just send your own first.<br>
<font color="#888888"><br>
--<br>
Fabio Forno, Ph.D.<br>
Bluendo srl <a href="http://www.bluendo.com" target="_blank">http://www.bluendo.com</a><br>
jabber id: <a href="mailto:ff at jabber.bluendo.com">ff at jabber.bluendo.com</a><br>
</font></blockquote></div><br>
------=_Part_25692_32597211.1210033774773--
More information about the Standards
mailing list