RE: [Simple] Status summary

Peter Saint-Andre <[email protected]>
Newsgroups gmane.ietf.impp
Message-ID <[email protected]>
In Jabber we handle this with the concept of a "resource" -- one Jabber
Entity (normally user@host) can possess multiple resources associated with
different connection types or locations (e.g., user@host/cellphone and
user@host/desktop), there is no limit on the number of simultaneous
connected resources that may be associated with a Jabber Entity, and each
resource can have a distinct presence status.

Peter

--
Peter Saint-Andre
email+jabber: [email protected]

On Mon, 15 Apr 2002, Boyer, David G (Dave) wrote:

> I am curious about something.  How would you catagorize present
> but on the phone?  You may not be available for a SIP audio session, but
> you would be available for an IM.  Different presence states for diff
> communication channels?
> 
> Dave
> 
> > -----Original Message-----
> > From: Sean Olson [mailto:[email protected]]
> > Sent: Monday, April 15, 2002 1:54 PM
> > To: [email protected]; [email protected]; Avshalom Houri
> > Subject: Re: [Simple] Status summary
> > 
> > 
> > There seems to be a common thread here where
> > we can map communication status (presence) to
> > one of three states:
> > 
> >    open,
> >    closed,
> >    undisclosed (invisible)
> > 
> > Is there a fourth type of state I am missing?
> > 
> > /sean
> > 
> > 
> > 
> > =====
> > Sean Olson <[email protected]>
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Tax Center - online filing with TurboTax
> > http://taxes.yahoo.com/
> > _______________________________________________
> > simple mailing list
> > [email protected]
> > http://mailman.dynamicsoft.com/mailman/listinfo/simple
> > 
> 
> 
> 
>   [reminder: [email protected] for non-technical discussions, please]
> 



  [reminder: [email protected] for non-technical discussions, please]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.