[jdev] Flash Proxy (was: Jabberd2, Flash Client...)

[Richard Dobson]

> another advantage of a protocol handshake
> is that it can be used to convey session, security, and
> application-specific details relevant to a given
> Flash client implementation.
>
> For instance, an application might want to transpose
> its security policy to the proxy session. It might need to
> connect on an alternative port due to firewall issues. And
> the Flash player might then need to load a 'shim'.

Yea there are all sorts of things the proxy could do to make the life of the
flash app much more easy, IMO if we just go ahead and hack the existing c2s
protocol to work with the flash proxy it will make it messy, harder to
understand for new comers, far more complex that it need be, and we miss a
big opportunity to make the proxy far more useful by adding all sorts of
features into it that the flash apps can take advantage of.

This is the perfect opportunity to help flash developers by making their
lives far easier when connecting to jabber servers all while retaining the
core strengths of the jabber protocol, the <presence> / <iq> / <message>
extensible stanzas, and the core stanza routing functionality, there is no
real reason to keep the <stream:stream> when it doesnt work as it was
indended with Flash anyway.

Richard