<br><br><div class="gmail_quote">On Sat, Feb 6, 2010 at 11:29 AM, Aristotle Pagaltzis <span dir="ltr"><<a href="mailto:pagaltzis@gmx.de">pagaltzis@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
* Bill Moseley <<a href="mailto:moseley@hank.org">moseley@hank.org</a>> [2010-02-06 17:30]:<br>
<div class="im">> As in don't provide a way to upload meta data along with the<br>
> file (name, date, description, author, title, reference id)<br>
> like the web upload allows with multipart/form-data? Or invent<br>
> some new serialization where the meta data is embedded in the<br>
> upload?<br>
<br>
</div>Neither, depending on your metadata. The things you did mention<br>
could quite well be sent as request headers. No need to put<br>
another envelope inside the HTTP request envelope. </blockquote><div> </div><div>Could you be more specific? For example API request to</div><div><br></div><div>1) create a new user in account #1234 with name, email, etc.</div>
<div>2) create a user but also provide a photo when creating the user</div><div>3) upload a document for the user and the document must include an associated collection of meta data (e.g. filename, timestamp, author etc.). The uploaded document must include</div>
<div>this meta data before it can be accepted.</div><div><br></div><div> </div></div><br><br clear="all"><br>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org">moseley@hank.org</a><br>