[ticker-dev] Re: Attribute Naming - user@domain debarcle

[Wanicki, Martin]

Sticking my nose in yet again,

Perhaps as in the presence spec where a single attribute is able to carry
multiple values, the user field is
mandated to also contain multiples values (at most two)
then *suggest* that folks keep the first part stable and do what they like
with the last part, ooh this is 
sounding like I'm an advocate for keeping things the way they are, oops :-)

I seem to remember a conversation about presence mentioning that the @domain
portion of a username has no meaning to 
the presence protocol, anyone remember that ??

So if presence clients actually ignore or strip out the @domain part of a
user field for identification purposes we get rid of all our problems
presence can still use this info a little like it uses client id.

ducks, weaves, runs like hell

martin