Dave,
That would also be problematic, since entities would then need to process
presence rather differently, even more so than they do for MUC now.
I was thinking simply:
<presence from='{{proxyjid}}' id='{{tracking id}}'>
<!-- ... -->
<mix xmlns='...'>
<jid/>
<nickname/>
</mix>
</presence>
[Steve Kille]
So what value is the proxy JID giving, given that the data which the client
might have derived from the proxy JID is now encoded in the message??
I was suggesting message came from coven@mix.example <mailto:coven@mix.example>
you are suggesting it comes from 5q3509q759348#coven@mix.example
<mailto:5q3509q759348#coven@mix.example>
What benefit is the proxy JID giving to the client?
Steve
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
_______________________________________________
