On 17/6/05 10:25 AM, "James M Snell" <[EMAIL PROTECTED]> wrote:
>> Something involving eTags would be the simplest from the client end. >> >> > Agreed, but it seems to be a bit of a trick to figure out what that > "something involvig eTags" could be ;-) > > None of the existing HTTP Headers that involve etags would seem to > account for the semantics of "return everything that's been modified > since..." http://www.google.com/search?q=atom+etags+diff+http&btnI=I%27m+Feeling+Lucky RFC3229? e.
