Has there been any thought put into the possibility of the Jive messenger playing the role of this kind of SOCKS 5 proxy - used in support of bytestreams in file transfer (JEP-0065)?
Was wondering because otherwise we would need to have a seperate proxy available for this purpose. Using direct connections between clients is not an option in our usage. As I understand it, JEP-65 stipulates some extensions to the SOCKS v5 protocol, so using a standard implementation would not work.
As I understand it, there is currently only a single implementation of this special Socks proxy - the proxy65 project available in jabberstudio. Its written in Python I believe.
Another useful feature () for our usage is that the file transfer be available even when the target is offline. The server would then store the file (for a bit like what Yahoo’'s server does) until the client does come online. It would be similar to what the server does for messages when a client is offline (ie stored in something like the JiveOffline table).