[jdev] Jabberd2, Flash Client and terminator character...

[Richard Dobson]

> > 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.

As I have already mentioned in my most recent email, it might be better to
create a proxy so the client can connect (via the proxy) to almost any
jabber server it wants, all we then need to do is dump the standard
<stream:stream> and develop a simple proxy control protocol to replace it,
to use in directing the proxy into connecting to the appropriate server and
what login credentials to use (the proxy can then handle any complex stuff
like the SASL etc), so using the proxy we can offload onto it the portions
of the protocol that are tuff or impossible to do directly in the flash, but
keeping the rest of the standard protocol.

Richard