[ticker-dev] Multiple presence clients for a single us er

[Wanicki, Martin]

I'm in favour of a Client-ID, but should there be some discussion as to its
use?

Like...

..	Should it be a unique ID generated each time a client starts al-la
Session-Id  ?

..	Should it be locked/tied to the machine upon which the client is
running ?
		and if so should it have a machine part and a client part 
		ie "Client-Id : Some_Unique_Id at Machine_Id" or something to
that effect?
		This sounds like it gives away too much privacy, but
presence is about giving 
		away information so it could be useful to be able determine
if one of the 
		clients for user "XYZ" on Machine "ABC" is currently in
"State" 

..	etc


These are just a few ideas, and I'm sure there's pro's and cons for them and
others.

I'm not advocating a particular scheme here, just offering up some
suggestions for debate.


Cheers


Martin


> ----------
> From: 	Phillips, Matthew[SMTP:Matthew.Phillips at dsto.defence.gov.au]
> Sent: 	Friday, November 23, 2001 10:01 AM
> To: 	ticker-dev (E-mail)
> Subject: 	RE: [ticker-dev] Multiple presence clients for a single us
> er 
> 
> Hello all,
> 
> this list seems to have died of late.  I was wondering if anyone had any
> comments on anything? ;)
> 
> In particular, I'd like to start implementing the standardized presence
> support in Sticker and, at this point, I am planning to use a Client-ID
> field to handle overloaded Presence-Info's.  I'll ensure it supports the
> current crop of presence clients which don't do the ID field though.
> 
> Cheers,
> 
> Matthew.
>