[Council] JEP - 0022

David Waite mass at akuma.org
Wed Apr 24 15:53:02 CDT 2002


There has to be some defined state for this case. Either the remote user 
is considered offline and composing, or the composing event is cancelled 
by the change in their availability.

-David Waite

Peter Saint-Andre wrote:

>This is informational. Perhaps we need a real standards-track JEP that is
>more complete, but this one is intended only to document the current
>protocol.
>
>Peter
>
>--
>Peter Saint-Andre
>email+jabber: stpeter at jabber.org
>weblog: http://www.saint-andre.com/blog/
>
>On Wed, 24 Apr 2002, David Waite wrote:
>
>>-1
>>Composing events need to have more cancelation methods than defined (for 
>>instance, is someone still composing if they go unavailable?) It seems 
>>like cancelation can either be explicit, or implicit through a change in 
>>presence or the availability of the session composing the message.
>>
>>Also, the 'offline' event needs to be defined as only being triggered by 
>>the recipient server (in a multi-server environment), only if offline 
>>storage is enabled, and only if the recipient server supports it. If 
>>this was a standards track, it could be defined that recipient servers 
>>must support it, but as informational it is completely optional and I 
>>would like the behavior in these cases to be explicitly stated.
>>
>>Rather good otherwise,
>>-David Waite
>>
>>_______________________________________________
>>Council mailing list
>>Council at jabber.org
>>http://mailman.jabber.org/listinfo/council
>>
>
>_______________________________________________
>Council mailing list
>Council at jabber.org
>http://mailman.jabber.org/listinfo/council
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://jabber.org/pipermail/council/attachments/20020424/03cfe5d6/attachment.html


More information about the Council mailing list