RE: [Simple] Status summary

"Ben Campbell" <[email protected]>
Newsgroups gmane.ietf.impp
Message-ID <[email protected]>
It seems to me this concept is still more intended for _human_ consumption.
It would be dangerous to provide any protocol semantic or other automatic
processing based on the assumption that I will be back at a certain time,
unless we build in explicit expiration times for the piece of state.

So, all of the following can be handled by some sort of "away" status that
contains a human readable comment (or some other indicator for user display
purposes only).

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Tony Hansen
> Sent: Wednesday, April 17, 2002 1:15 PM
> Cc: [email protected]; [email protected]
> Subject: Re: [Simple] Status summary
>
>
> One aspect that hasn't come up yet in this conversation is something
> someone said at the ad-hoc mtg in MN: the temporal aspect of the various
> types of OPEN status messages. Why do you choose to use one message over
> another? Usually it's to give the others an idea of how quickly you'll
> respond.
>
> Some of them mean "I'm doing stuff, but will probably respond to your
> message pretty quickly." (T = a couple minutes) Examples: Busy, On the
> Phone.
>
> Some of them mean "I'm going to be gone for a while." (T = 1/2 - 1 hour)
> Example: Out to Lunch.
>
> Some of them mean "Don't expect me to respond for hours." (T = 2-4
> hours) Example: Away, In Meetings.
>
> Some of them mean "Don't expect me back for a long time." (T > 4 hours)
> Example: Out for the weekend.
>
> When you go international, Out to Lunch doesn't mean a whole lot to
> anyone but English speakers. But specifying an expected time to be gone
> set at .5-1 hour certainly does translate well. Time is a pretty
> universal concept, and might be worth codifying as part of the status
> information.
>
> 	Tony Hansen
> 	[email protected]
>
> _______________________________________________
> simple mailing list
> [email protected]
> http://mailman.dynamicsoft.com/mailman/listinfo/simple



  [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.