[standards-jig] JEP-85: Chat State Notifications
dizzyd at jabber.org
Mon Jul 21 04:26:12 UTC 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Sunday, Jul 20, 2003, at 21:42 America/Denver, Peter Ronez wrote:
> Anyway, the reason why I started looking at JEP-85 in the first place
> is b/c I
> ran into a road block with plain jabber:x:events -- I need the 'gone'
> from JEP-0085. However, the feature that I'm working on made use of
> the message
> ID being sent along with composing events. JEP-85 doesn't have a way to
> communicate message IDs for events, and so to get around this, I
> believe this
> is why thread ID was added as an optional element.
> Unfortunately, this solution isn't sufficient since I need a finer
> than the thread ID, I need the message ID that the event is associated
> with. My
> rationale for this is that thread IDs encapsulate a conversation and
> IDs of course single out a message in that conversation.
Before I respond to this, can you please provide a little more context
about why you need finer granularity than a "conversational" (i.e.
thread) level event? I'm not sure what a "gone" event means, when
applied to a single message...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)
-----END PGP SIGNATURE-----
More information about the Standards