On 12/7/06 3:38 AM, "Joe Gregorio" <[EMAIL PROTECTED]> wrote:
>> As far as I can tell, the string values that would go into app:modified are >> just as opaque as the string values one might find in @etag, and so are at >> least as useful. > > Yet they have the potential weakness of > having too much granularity, opaque is opaque, there is no granularity. > they are a re-invention of Last-Modified:, no more than @etag is of Etag: > they don't solve the lost update problem, neither does Etag > and they don't solve the ambiguity of app:modified we're writing the spec, which means we can address that ambiguity. Are we really trying to figure out some "perfect" magic bullet that fixes all the problems while avoiding all the various weaknesses, plus cooks an English breakfast? e.
