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. - James
- Re: Modeling the info in APP Service documents James M Snell
- collections feeds versus "subscription&q... James Tauber
- Re: collections feeds versus "subscr... Thomas Broyer
- Re: collections feeds versus "subscr... James M Snell
- Re: collections feeds versus "s... James Tauber
- Re: collections feeds versus &qu... Tim Bray
- Re: collections feeds versus "subscr... David M Johnson
- Re: collections feeds versus "subscr... Eric Scheid
- Re: Modeling the info in APP Service documents Henry Story
- Re: Modeling the info in APP Service documents Henry Story
- Re: Modeling the info in APP Service documents James M Snell
- Re: Modeling the info in APP Service document... John Panzer
- Re: Modeling the info in APP Service docu... James M Snell
- Re: Modeling the info in APP Service... Henry Story
- Re: Modeling the info in APP Ser... James M Snell
- returning an entry in POST to me... Henry Story
- Re: returning an entry in POST t... James M Snell
- Re: returning an entry in POST t... Henry Story
- Re: returning an entry in POST t... Eric Scheid
- Re: Modeling the info in APP Ser... Eric Scheid
- Re: Modeling the info in APP Service... John Panzer
