On Sep 8, 2009, at 3:14 PM, Peter Saint-Andre wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9/8/09 3:46 PM, Kurt Zeilenga wrote:
On Sep 8, 2009, at 1:53 PM, Peter Saint-Andre wrote:
The recent discussion about namespaced attributes on the
[email protected]
list set me to thinking about the separation of routing information
and
payload data.
Below you use <header/> in your examples, which per XEP-0131 is for
"non-addressing information about the stanza", which seems to be
payload
data to me.
Sort of. :)
Could you revise your suggestion to discussing moving say
<addresses/>
[XEP-0033] information, which is more obviously routing information,
into attributes of the stanza?
One can do that in one's own mind.
Well, in my mind, I don't see how to, in a straight-forward way, map
the examples in section 3 and 4 of XEP 33 into attributes of the
stanza. One would likely end up with an attribute of:
addresses:addresses="base64-of-addresses-element"
Which doesn't seem terribly desirable, so I wonder if you had
something else in mind.
I have to wonder how this might compare to the old "envelope"
approach
referenced in XEP-0033. I'd compare it myself but I couldn't find a
copy
It never was in the inbox. I've had to resurrect it here:
http://archive.jabber.org/docs/proto-draft/envelope.html
Thanks.
Okay, so this is similar to the XEP 33 approach (and unlike your
approach) in that it places routing information in a child element of
the stanza.
-- Kurt
