[standards-jig] Comments on JEP-85: Chat State Notifications

Dave Smith dizzyd at jabber.org
Thu Jun 5 22:59:21 UTC 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Julian,

Perhaps you can elaborate a bit on what you would cleanup and how?

Thanks..

D.

On Thursday, Jun 5, 2003, at 10:10 America/Denver, Julian Missig wrote:

> On Thursday, Jun 5, 2003, at 10:52 US/Eastern, Dave Smith wrote:
>
>> Greetings,
>>
>> Are there any outstanding concerns/complaints about JEP-85? I'd like 
>> to start building consensus around it so we can get the Council to 
>> ratify it.
>>
>> Thanks.
>>
>> Diz
>
> I don't want to be rude or anything, but...
>
> I'm still pretty unconvinced that message events need to be replaced 
> to begin with. I can see getting rid of having the x:event be in 
> messages that are sent and relying on browse/disco to detect that 
> feature.
>
> I also don't generally see cases where we want to tell people to 
> temporarily stop sending composing events where it's really worth the 
> added protocol complexity.
>
> Basically, I'm pretty happy with the message events we have now. I 
> could see making a few changes and such to simplify and remove extra 
> cruft we don't need in the age of Disco, but I really don't want to 
> have to implement both message events and chat state notifications, 
> which means that chat state notifications would probably have to 
> replace message events. We already have tons of clients, transports, 
> etc. implementing message events--I think it would be more beneficial 
> just to clean them up than to create a whole new thing.
>
> Julian
>
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iD8DBQE+38tJYNE3chVHHsMRAulgAJ9KI7WULd4qadij40fV5ae3ibNWfgCg/TzT
nllP8rRQ3j2pFo7rW7Eq4SY=
=Z/59
-----END PGP SIGNATURE-----




More information about the Standards mailing list