Hi I've been looking at alternatives for large file transfer within the jabber framework. As mentioned before, I undertand that architecturally, the 'jabber way' is to move the problem somewhere else by passing an address oob and handling access outside fo jabber.
For my purposes, I'm looking for something more tightly integrated (sharinf jabber's model of transactions etc). I'm interesting the Proxy Accept Serice, but I can old find one seemingly partial implemenatation (at http://cataclysm.cx/jabber/pass.html). So for the moment, I'm back to thinking about embedding files in messages. For large binary files of course base64 sucks. But it would suck less where the whole xml stream decently compressed on the way between client and server. Does anyone know of any way of doing xml xtream compression either: - within jabber itself, or - via a utility which does for compresion what stunnel does for encryption (function as an IP socket-based proxy) -- i.e tell it which port to listen on, and which port to respond on and it will operate transparently between the originater of the data (jabber) and another instance of itself on another machine connected to another instance of jabber... Does any of that make sense? Any input would be very useful. thx
smime.p7s
Description: application/pkcs7-signature
