Re: [Standards] roster item exchange
On Mon, Apr 6, 2009 at 12:36 AM, Peter Saint-Andre wrote: > I haven't looked at XEP-0144 in a long time, but IMHO it would be fairly > straightforward to add this kind of optional notification. I'd be happy > to work with you on that. Great! we have just implemented in a facebook gateway and in Lampiro a great deal of xep 144 and pep for avatars and we found few quirks and possible optimizations that will improve user experience. I know that we shouldn't encourage too much transports (they must be painful! :D), but the ability of manipulating from another entity the roster is terrific for automatically adding/changing services accordingly to the user context. Tomorrow or in the next days we can catchup via jabber for exchanging ideas. Now it's 2am here, better go to bed ;) -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: f...@jabber.bluendo.com
Re: [Standards] roster item exchange
Ciao Fabio! On 12/29/08 2:42 PM, Fabio Forno wrote: > Hi, > > we are writing a facebook gateway and we'd like to use xep-144 for > pushing roster items to the client. Besides the fact that it seems > implemented by few clients, I've found another problem. With xep 144 > the gateway has no means for knowing whether the user has accepted the > presence subscription or not, just that the client has processed it > (the result iq is sent as soon as the roster offer has been received). > This leads to two unpleasant case: > - if the gateway assumes that the items have been accepted and the > user does some mistakes (or the client dies), he won't be able to see > the contacts any more > - if the gateway always sends the roster push we have either > unnecessary traffic and the user may be bothered with subscriptions he > doesn't want to accept > > The problem is that I don't see any workaround but extending the xep > notifying the gateway which contacts have been accepted and which not I haven't looked at XEP-0144 in a long time, but IMHO it would be fairly straightforward to add this kind of optional notification. I'd be happy to work with you on that. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
[Standards] roster item exchange
Hi, we are writing a facebook gateway and we'd like to use xep-144 for pushing roster items to the client. Besides the fact that it seems implemented by few clients, I've found another problem. With xep 144 the gateway has no means for knowing whether the user has accepted the presence subscription or not, just that the client has processed it (the result iq is sent as soon as the roster offer has been received). This leads to two unpleasant case: - if the gateway assumes that the items have been accepted and the user does some mistakes (or the client dies), he won't be able to see the contacts any more - if the gateway always sends the roster push we have either unnecessary traffic and the user may be bothered with subscriptions he doesn't want to accept The problem is that I don't see any workaround but extending the xep notifying the gateway which contacts have been accepted and which not -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: f...@jabber.bluendo.com
