Re: [Standards] Group Name with Gateway Registration
Ian Paterson wrote: Currently the name of the group that contacts will be added to tends to be hardcoded on the gateway. This causes problems if there are language issues or, more typically, if the user has two accounts on a legacy service (accessed via two instances of a gateway server) - in which case the contacts will end up being mixed within the same group. To solve this I'd suggest adding a new example (see [1] below) to Section 7 "Contact Lists" that indicates how the client/user might specify during registration a group name (see the "group" below) that the gateway will use whenever it adds contacts to the user's roster. Someone mentioned offlist that some legacy services now support groups, and that some gateways now use these group names (instead of a single hardcoded group). So it may be useful for the client to be able to indicate a prefix/suffix for all group names, instead of a single prefered group name. (A zero length prefix/suffix would be equivalent to no change to the group names at all.) I'd suggest a second additional field like the one in the examples below. - Ian SERVER SENDS: . . . var='groupmodify'> prefix suffix fixed . . . CLIENT SENDS: . . . suffix (Yahoo Work) . . .
Re: [Standards] Group Name with Gateway Registration
Tomasz Sterna wrote: Dnia 15-08-2007, śro o godzinie 18:31 +0100, Ian Paterson napisał(a): Currently the name of the group that contacts will be added to tends to be hardcoded on the gateway. You are talking about gateway XEP-0144 usage? Yes, or the direct roster editing that some server-hosted-plugin gateways seem to perform. - Ian
Re: [Standards] Group Name with Gateway Registration
Dnia 15-08-2007, śro o godzinie 18:31 +0100, Ian Paterson napisał(a): > Currently the name of the group that contacts will be added to tends > to be hardcoded on the gateway. You are talking about gateway XEP-0144 usage? -- Tomasz Sterna Xiaoka Grp. http://www.xiaoka.com/
Re: [Standards] Group Name with Gateway Registration
Ian Paterson wrote: > Currently the name of the group that contacts will be added to tends to > be hardcoded on the gateway. This causes problems if there are language > issues or, more typically, if the user has two accounts on a legacy > service (accessed via two instances of a gateway server) - in which case > the contacts will end up being mixed within the same group. > > To solve this I'd suggest adding a new example (see [1] below) to > Section 7 "Contact Lists" that indicates how the client/user might > specify during registration a group name (see the "group" > below) that the gateway will use whenever it adds contacts to the user's > roster. I've been asked offlist if the communities / shared groups spec that Bruno van Haetsdaele and I are working on as a follow-up to the XMPP devcon might apply to gateways as well. I think it might (essentially, the gateway manages a contact list for you). Ideally you could name (or later rename) that list. I'll add that to the use cases we're addressing in the communities spec. But in the meantime what you propose for XEP-0100 seems sensible. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
[Standards] Group Name with Gateway Registration
Peter Saint-Andre wrote: Ian Paterson wrote: Peter Saint-Andre wrote: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0100.xml?%40diffMode=u&%40diffWrap=s&r1=1092&r2=1134&u=3&ignore=&k= TinyURL: http://tinyurl.com/2dxv5j That looks good, thanks :-) Super, I've added that to the agenda for the next Council meeting: Since we're already making a couple changes to this XEP, can we consider including a recommended fix for the issue below: Currently the name of the group that contacts will be added to tends to be hardcoded on the gateway. This causes problems if there are language issues or, more typically, if the user has two accounts on a legacy service (accessed via two instances of a gateway server) - in which case the contacts will end up being mixed within the same group. To solve this I'd suggest adding a new example (see [1] below) to Section 7 "Contact Lists" that indicates how the client/user might specify during registration a group name (see the "group" below) that the gateway will use whenever it adds contacts to the user's roster. - Ian [1] CLIENT SENDS: to='aim.shakespeare.lit' id='reg2'> jabber:iq:register RomeoMyRomeo ILoveJuliet AIM (Work)
