[Standards-JIG] Re: JEP-0096: File Transfer HTTP mechanism
ian.paterson at clientside.co.uk
Thu Sep 2 17:27:02 UTC 2004
> jabber:iq:oob in fact doesn't say anything about how you put or get
> files via HTTP -- all it really does is provide a way of communicating a
> URI (which need not be an HTTP URI).
Yes. It is very generalised. But it works.
> > The HTTP mechanism could be 'jabber:iq:oob' (see the File
> > Transfer example in JEP-95 Stream Initiation). In that case,
> > IMHO, JEP-66 would need to be redesignated as 'standards track'.
> This is worth considering, IMHO.
Can we also consider adding some basic metadata fields (optional for
backward compatability of course).
> BTW, http://www.jabber.org/jeps/jep-0129.html may be of interest as well.
Yes, interesting. Unfortunately it would not be possible to adapt that JEP,
More information about the Standards