-David Waite
On Apr 12, 2004, at 12:52 PM, Richard Dobson wrote:
g so there is not much point continuing this here, lets just get onto the relevant subjects in hand.
Overall as has been said because of the limitations in Flash there are several options in order of preference.
1) Lobby macromedia into if not providing proper jabber support into
providing a more flexible xml parser system that can support xml streams,
and into providing a more flexible sockets infrastructure, this will mean
full compatibility with standard Jabber/XMPP servers.
2) Use JEP-124 HTTP polling, this will also mean using a standard protocol
and so will work with most Jabber/XMPP servers that have deployed this, and
does not require any flash custom hacks which as others have noted are a
very bad thing to propergate now we have proper standardised protocols.
3) Create a proxy between Flash and the Jabber/XMPP server, this means
either you have to rely on server admins to install this gateway with their
jabber installtions (an unlikely possiblity IMO) or you (as the flash
application developer) have to host it yourself.
4) Lobby the jabberd2 developers into implementing the flash specific hacks
that are against the established protocol specs, this is bad because it
propogates bad hacks, it also means your flash apps will only work with
jabberd2 servers and will not work with all the other jabber/xmpp
implementations out there, also your flash apps might stop working sometime
in the future if these hacks get removed or changed. Overall this is the
worst possible solution to the compatibility problem.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
