On 10/15/05, Tim Bray <[EMAIL PROTECTED]> wrote: > > On Oct 15, 2005, at 6:24 PM, Joe Gregorio wrote: > > > I thought there was pretty strong support on list that the client > > MUST do a GET on the member resource before editing. > > That's news to me, and not reflected (I think) in any drafts. I also > would tend to disagree, from first principles. Suppose I have a feed > that contains price reports on ten equities, and I overwrite them > with a succession of PUT calls once per minute. I know perfectly > well what URI to send each equity price to, and it seems unreasonable > to make me GET it first, when I'm just going to overwrite it. -Tim > >
In the thread in question Joe said: "Given that no one has spoken in support of Full Entries in query responses I believe that Minimum Entries should be the default behavior, or more precisely, the spec should state that the client MUST NOT presume the entry in the feed is a Full Entry." I think that allows for your case. You are not presuming. You know that you have complete entries. +1 to "MUST not presume" Perhaps something should be stated explicitly about performing a GET as well. - Luke
