Re: Modeling the info in APP Service documents

[John Panzer]

James M Snell wrote: Henry Story wrote: Oh dear! I just found out why I got a little confused. Section 8.1.1 only shows the header returned in the POST. Whereas the example in section 12 (Atom Publishing Protocol Example) shows the entry returned in body of the post to the media collection. So I suppose things are working as I thought. 1. Posts to entry collections just return the header 2. Posts to media collections return an entry The example in Section 12 is incorrect. No where in the spec does it say that a post to a media collection returns an entry. The example is showing a "feature" that doesn't exist. Can someone remind me again of the current status:  How would a client, written defensively so that it doesn't assume the server returns the entry rep when posting to a media collection, retrieve the viewable URL of a cat picture for use in embedding inside an actual entry containing both pictures and text? <content ..><img src="" class="moz-txt-link-rfc2396E" href="http://example.org/media/pictures/cat001.jpg">"http://example.org/media/pictures/cat001.jpg"/>Hey, look at this cool cat!</content> If the answer is "you have to retrieve the entire media collection and walk through it, looking for the picture you just posted"... well, I really don't want to have to stand up and tell people that when I'm trying to evangelize the APP.  Especially to people who are dealing with applications with potentially thousands of pictures in a collection. -John