[Standards] Jingle initiate and resource determination
ian.paterson at clientside.co.uk
Wed Jun 6 16:35:33 CDT 2007
Peter Saint-Andre wrote:
> Having re-read your namespace priority idea, I think it has merit.
> One challenge I see is synchronization of namespace priorities across
> resources. We already have this to some extent with standard XMPP
> presence priorities (oh damn I left my desktop priority as 99 and now
> I need to use remote controlling to change it there, or make my
> priority here 100). But with presence priorities at least the numbers
> are broadcasted to all of your other resources. AFAICT we would not
> have that with the IQ-based namespace priorities unless there would be
> some kind of "NP-push".
Yes. And pushes would only be necessary where two resources advertise
support for the same namespaces.
> The more I ponder forking of headline messages, the more I like that
> idea, because it also works for plain old chat sessions. Currently
> Google Talk sends all messages to all resources but they need a fancy
> coordination protocol to retract messages that are not of interest to
> other resources. If the initial message in a chat session (or the
> stanza session negotiation request) is of type headline and all the
> others are of type "chat" then you get only one message at the other
> resources (and we could even give that a TTL so the receiving clients
> at your other resources throw it away after a certain time).
More information about the Standards