Well, I've personally seen this use case appear in the wild. It does happen. :) It's perfectly legitimate XML and XMPP as far as I know. The case I have seen was a .NET exception object serialized to XML and being passed through an XMPP message. It was an asynchronous RPC sort of scenario. As you can imagine there was a message element containing the error message nested in the .NET serialization output in the exception object.
JD Conley > -----Original Message----- > From: Anthony Ortiz [mailto:[EMAIL PROTECTED] > Sent: Friday, March 11, 2005 8:19 PM > To: JD Conley; Jabber software development list > Subject: Re: [jdev] My outgoing jabber packet > > Hahaha!! True, true... I thought about that briefly but I could not > find a single instance in the jabber specification where nested tags > with the same name occur... I think I even read somewhere that this > would never be the case, though now that you mention it you're raising > some old doubts again. If so, then I would definitely have to throw > out my regex parsing and use a stack mechanism instead since I don't > think regex can handle such a case. Anyone have any thoughts on > whether the jabber spec allows for such unruly contraptions?? :p > > Anthony > > > On Fri, 11 Mar 2005 18:49:39 -0800, JD Conley <[EMAIL PROTECTED]> > wrote: > > Don't forget: > > > > [Packet 1] > > <message> > > <message xmlns="mynamespace"></message> > > [/Packet 1] > > > > [Packet 2] > > </message> > > [/Packet 2] > > > > Throw that one at your RegEx. :) > > > > JD Conley > > _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
