RE: Indicate entry in Collection Feed is full representation

["Brian Smith" <brian@xxxxxxxxxxxxxx>]

Teo Hui Ming wrote:
> On Dec 1, 2007 12:47 AM, Brian Smith <brian@xxxxxxxxxxxxxx> wrote:
> Since my entry data is light-weight, it's fine to include 
> full representation entries in the feed. When a client wish 
> to edit an entry, the le:etag becomes useful as the client 
> can use it to send a conditional GET to validate whether the 
> entry is up-to-date, if not valid, the server simply returns 
> an updated copy. If valid, the client will just process the 
> <entry> element in the feed, since it is a full 
> representation. That's my intention.

In the original message, you said you wanted to reduce the number of round-trips, but this ends up being the same number of round-trips as is currently required. Furthermore, since the entries are small, there would be little difference between the "304 Not Midified" and a "200 OK": you would only save one or two packets, and most of that savings is eaten by the bloat in the collection feed. In order to be really useful, an extension like you mention would have to assure the client that it replace the conditional GET on the entry resource with a (conditional) GET on the feed.

- Brian