hi, what is the best practice (interpretation of APP) for including <atom:entry> entity in 201 Created HTTP response to POST of new resource? is <atom:entry> entity required for media collections? especially when Location points to binary content? this is very confusing as in draft-08 there are two different examples: section 8.1.1 vs. section 12?
is it allowed to POST atom:entry with binary content to media collection? [1] for entry collections: is it allowed that <atom:entry> POSTed has no atom:id so the atom:id is assigned by server? in that case should <atom:entry> be returned in 201 Created response to let client know that it needs to update its representation of atom:entry (and get required atom:id)? how are current implementations of APP dealing with it? are there available captures of HTTP traffic for perusing (something like [1]) thanks, alek [1] is this valid interaction with media collection? POST /media HTTP/1.1 User-Agent: Client/0.9.99-AT3 Authorization: Basic YAAAAAA Host: localhost:7070 Content-Length: 149 Content-Type: application/atom+xml; charset=utf-8 <atom:entry xmlns:atom="http://www.w3.org/2005/Atom";><atom:title>some.png</atom: title><atom:content type="image/png">AQID</atom:content></atom:entry> HTTP/1.1 201 Created Location: http://localhost:7070/2005/07/21/entry110.atom Content-Length: 0 Date: Fri, 14 Apr 2006 20:56:12 GMT -- --- Memorable Quote from Firefly (105. Out Of Gas) -Ship like this, be with you until you die -That's because it's a deathtrap
