On Fri, Sep 08, 2017 at 02:11:06PM +0200, Philipp Hörist wrote: > Conversations implements and uses Jingle for FT. > And Dino is a bit new and i think there are more important things on the > TODO list then jingle. > Switft and Gajim also implement Jingle.
Yes, file transfer over Jingle with Gajim and Conversations has worked well in my experience (more on that below). > Im with you that it is not easy to implement, mostly because i have to do > low level socket stuff, compared to HTTP Upload where i can upload and > download a file with one line of code in python. > > My opinion is that its overkill to use Jingle for a use case where i want > to transfer/publish a small file to a server. As i said i can do this with > one line of code in python using http, i think its the same in other > languages. In the case of small files, Jingle with IBB is a bit nicer and cleaner, since it doesn't require a client/server to implement any "non-XMPP" things (making it much less "overkill" in a sense). This is a big reason why we chose to use Jingle with IBB in https://jmp.chat/ (an XMPP bridge that gives you a phone number for text/picture messaging) - you can see how we implemented it here: https://gitlab.com/ossguy/sgx-catapult/blob/b5902e0/sgx-catapult.rb#L406 Jingle with IBB also has the advantage of working basically everywhere. Inband means you don't have to worry about firewalls or proxy servers or anything else that might be in the client's way. The fact that the client has an XMPP stream means that Jingle with IBB will work for them. Denver https://jmp.chat/ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
