Well, As far as I understand JEP-0124, it mean that the Flash client would need to poll the3) Develop alternatives to direct XMPP streams
Let's see if we can make JEP-0124 do the right thing.
For Option #3, I believe there is already something in the works, in the form of JEP-0124: HTTP Binding. It's not ideal, but given the fact that it can much more easily accomodate the demands from both XMPP and Flash. The problem, of course, is that JEP-0124 is still rather immature, and lacks any truly deployable implementations.
Well, it's a fairly new JEP. I know of several folks working on implementations, but not all of them will be open-source.
server, right? I dont think that the best way to go since as some others pointed it out, Flash
would lost a lot of resource in creating / destroying HTTP calls and it does not provide real-time
behavior.
A compatibility layer between Flash and Jabber2 would be the best way to go IMHO.
The thing I m wondering (due to my lack of knowledge concerning jabberd2 architecture),
is what form this compatibility layer should have? Jabber Component? If yes, Internal or
External ?
johann
Then again, if the Flash-XMPP/Jabber community does not feel this is adequate, they are welcome to present better alternatives.
As always. :-)
/psa
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
