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

[Richard Dobson]

> What if the Flash c2s code were implemented as a J2 transport ?
> * Is the 1.4 version portable to J2 ?
>
> Official support could be accommodated by JEP-124, or
> some other HTTP bound JEP.
>
> Flash requires a socket protocol transformation,
> not a xmpp definition. In fact, it's when you attempt
> to define a Flash session that you corrupt the
> xmpp stream. So IMO we should externalize
> 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.
>
> does this make sense ?

Kind of although it would be far better to have a flash CCM rather than a
transport, a transport wouldnt really work in this instance as a transport
is intended to allow jabber users who are already connected to their jabber
server to connect to other IM systems too via the existing jabber
connection.

Also as Sean rightly points out this Flash CCM/Proxy component would have to
be hosted on the same server as the webserver serving the flash file anyway
because of the flash security sandbox.

So this should definately be a separate component from from the core server
anyway and it certainly shouldnt be required to implement either as not
everyone will need it or want it. IMO we need two components, a CCM
component for people who whose flash apps will only ever connect to their
own jabber server, and a proxy component that will allow flash components to
log into any jabber server from their flash apps via the proxy.

Richard