I don't even know whether this is supported w/ the newest Flash player. You're right though, it'll try to parse any xml - even invalid xml, hence the stream element issue.
So perhaps externalizing Flash stream handling is the best approach. I'm thinking of a simple component that intermediates sessions between a Flash player and J2 server, conforming their respective streams. So the component provides J2 w/ a compliant XML stream, and handles all of the null byte weirdness required by the XMLSocket object. The question then is which JEPS a/o other features are broken by this approach ? > > The XMLSocket object does transmit simple strings. This might provide a > > work-around for the stream element issue, but I'd want to confirm future > > support for this 'feature' w/ macromedia. > > My experience is that even when you pass the XMLSocket.send() method a > string representing the XML, rather than XML itself, it still converts it > to XML and adds the terminating / (along with the zero byte). It's > possible that if you pass a string without the <>, Flash might interpret > it as normal string instead, but I don't see this as useful. > > - Sean > > Sean Voisen > Weblog: http://voisen.org > Flash/XMPP: http://xifflabs.com > XIFF 2.0: http://www.jabberstudio.org/projects/xiff > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > https://jabberstudio.org/mailman/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
