On Tue, 13 Apr 2004, dlb wrote: > the Flash c2s as a 'transparent' transport. Then we > could do away w/ the <flash:stream> scheme > and simply dedicate flash connections to a given port.
Interestingly enough, I was discussing these issues with a server developer last night, and he devised a similar solution. Honestly, as cool as it would be to see official support in a JEP for this, I agree that it's probably unnecessary because, like you said, it's not really a protocol issue. It's simply a difference in how the socket communication works. Flash alone, in its current state, will never totally be XMPP compliant. It's limited in capabilities in this matter and I'll just have to accept that - no SSL is a big one. I did manage to get Flash into not appending the terminating slash / to the opening <stream:stream> tag, so it's really just a matter of the zero-byte. - 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
