Am 25.11.2008 um 15:40 schrieb Dirk Meyer:
IMHO Jingle should be part of any client. File transfer over Jingle ismuch better than the normal one. You can change the transport if it does not work. And Jingle itself is very simple and not that hard to code. Ifyou want to support RTP over Jingle for a VoIP client, it is much more complicated. Jingle itself is just negotiate a session, fire up IBB or SOCKS5 (which you have for file transfer anyway) and that's it.
Well, why would a mobile client want that? You won't transfer files from your cell phone, will you? But you will chat with it. And if you chat with it, you want encryption.
I guess the problem for Jingle is, that the XEP uses VoIP as example. Take a look at XEP 0234 (Jingle Filetransfer). It is much easier to understand and more similar to the Jingle security stuff.
I have to admit that I haven't read Jingle Filetransfer yet, but had a look at the other Jingle XEPs which I consider too complicated.
-- Jonathan
PGP.sig
Description: This is a digitally signed message part
