Re: [Standards] Proposed XMPP Extension: HTTP File Upload

2015-08-07 Thread Mickaël Rémond
Hello, We had a try at changing a bit our approach for HTTP-based file transfer to support use cases, pointed out by Sam and Daniel. The result is here: https://github.com/processone/ejabberd-saas-docs/blob/master/xmpp-specs/http-filetransfer/http-filetransfer.md What we changed is: -

Re: [Standards] Proposed XMPP Extension: HTTP File Upload

2015-08-07 Thread Mickaël Rémond
Hello Philipp, On 30 Jul 2015, at 20:12, Philipp Hancke wrote: HTTP Upload is just another transport as far as jingle is concerned. So you would send your session-initiate with the XEP-0234 description (instead of reinventing this in example 5) along with an empty transport/ qualified by

Re: [Standards] Proposed XMPP Extension: HTTP File Upload

2015-08-07 Thread Mickaël Rémond
Hello Sam, On 1 Aug 2015, at 21:51, Sam Whited wrote: If you're going to try and implement a version of your spec with headers and test it against a particular service, I recommend AWS S3 (I've been using it as an example as it's probably the most common large file storage solution [citation