[JDEV] Re: JEPs and Jabber Adoption -- Clarification

[GuruJ]

While I am sure there are many more qualified than me to comment on 
these JEPs, I'll throw these suggestions into the ring anyway...

Paul Curtis wrote:
> JEP-0096 File Transfer Stream Initiation Profile
> http://www.jabber.org/jeps/jep-0096.html

The main omission I can see in this JEP is that allowances should be 
made for both Ascii and Binary file transfers, particularly so that 
proper Unicode compliance can be achieved and so on.

Also, to me it seems a little strange that a /File Transfer Stream/ JEP 
should say that SOCKS5 MUST be supported, but makes no mention of FTP, 
HTTP or any of the other commonly supported protocols.

I understand the logic (because socket streams make more sense for P2P 
applications), but to me it would be very handy to have the option to 
present files for download based on a remote URL.

This would change the JEP so that streams could be listed as follows:

     <feature xmlns='http://jabber.org/protocol/feature-neg'>
       <x xmlns='jabber:x:data'>
         <field var='stream-method' type='list-single'>
           <option><value>s5b</value></option>
           <option><value>ibb</value></option>
           <option><value>http</value></option>
           <option><value>ftp://ftp.jabber.org/file.txt</value></option>
         </field>
         <field var='stream-urls' type='list-single'>
           <option>
             <type>http</type>
             <value>http://jabber.org/file.txt</value>
           </option>
           <option>
             <type>ftp</type>
             <value>ftp://ftp.jabber.org/file.txt</value>
           </option>
         </field>
       </x>
     </feature>

Obviously, this isn't 100% necessary, but the implementation of such a 
feature would be fairly trivial and could be very useful.

-- GuruJ.