Andreas Monitzer wrote: > On Mar 16, 2009, at 13:09, Dirk Meyer wrote: > >> Yes, maybe restrict the usage to a stanza and not allow it inside a >> stanza by default. So a client MAY send any return from any XEP out of >> band, but only the whole result. If out of band is allowed somewehere >> deep inside a stanza it SHOULD be added to the XEP defining that >> namespace. > > That's not a good idea, since then you couldn't use it for binary data > at all (since you never have base64-encoded data at the top level). > Having it only in specific stanzas would mean that you couldn't > implement a solution for everything, but only on a case-by-case basis > (or you'd have to carry around a list of situations where it's allowed > – ugh).
Yes, but on the other hand it would be a pain for the developer to expect out of band data everywhere. And it is not needed in most cases. Maybe use the service discovery to handle the list: <feature>urn:xmpp:jingle:apps:out-of-band:0</feature> <feature>urn:xmpp:tmp:media:server+outband</feature> This means that the client expects out of band data as first child element in any stanza and inside every element in the media server namespace. I know it kind of sucks to carry the list around. Another way would be that the urn:xmpp:tmp:media:server namespace defines where out of band data may happen. So if you support out of band data, just must expect for every complete stanza and everytwhere in the media server namespace where it is defined. No idea what the best solution is. Dirk -- Drugs cause amnesia and other things I can't remember...
