On Tue, Feb 2, 2010 at 4:37 PM, Peter Saint-Andre <[email protected]>wrote:
> The numerical approach to status codes is ugly: > > <presence > from='[email protected]/thirdwitch' > to='[email protected]/pda'> > <x xmlns='http://jabber.org/protocol/muc#user'> > <item affiliation='member' role='participant'/> > <status code='110'/> > </x> > </presence> > > I think it could be easily extended as we did for core XMPP stanza errors: > > <presence > from='[email protected]/thirdwitch' > to='[email protected]/pda'> > <x xmlns='http://jabber.org/protocol/muc#user'> > <item affiliation='member' role='participant'/> > <status code='110'> > <self-presence/> > <status> > </x> > </presence> > > The question is: should the new child elements be qualified by a > namespace other than muc#user? I think that would be cleaner and less > likely to cause problems, because XMPP implementations ignore data from > unknown namespaces. That would be kinder to existing frameworks - i.e. as I use JAXB then a child element would be easy to add using an alternate namespace and as you say it would ignore any unknown namespaces (well not quite ignore but it would be ignorable. Peter -- Peter Mount e: [email protected] w: http://retep.org xmpp:[email protected] <xmpp%[email protected]> MSN: [email protected]
