On Wed, Feb 11, 2009 at 12:32, Martin Langhoff <martin.langh...@gmail.com> wrote: > On Wed, Feb 11, 2009 at 10:46 PM, Morgan Collett > <morgan.coll...@gmail.com> wrote: >> Yes, way back we found that tracking is_registered was unreliable, > > Fair enough. However, a number of operations on the client side need > to know whether Sugar thinks it is registered. > >> Ask the server? > > Hmmm, no. I just want to know if we're registered, separately from > talking to the server. > > We do need a bit of state on the client side to track whether it > thinks it is registered. We also need a workflow if it turns out that > it isn't registered, or that the server's been wiped clean after it > lost its marbles. But that's a separate issue :-) > >> Looks like 0.86 needs a new feature around registration management as >> we're significantly after the 0.84 feature freeze. > > Do you mean 0.84 has no concept of a 'registration' action like 0.82 did?
I mean if we need to reinstate the is_registered tracking, or something like that... I'm not sure of the status of the registration feature in 0.84 - all I can say authoritatively is that from a jabber server connection perspective, PS always automatically tries to reregister if necessary. I don't know off hand what else the register function for the XS does in terms of state in Sugar. HTH Morgan _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel