- From: Geoffrey M. Clemm <gclemm@tantalum.atria.com>
- Date: Sun, 23 May 1999 23:21:53 -0400
- To: francis@ecal.com
- Cc: ietf-dav-versioning@w3.org, w3c-dist-auth@w3.org
From: John Stracke <francis@ecal.com> Yaron Goland wrote: > Modeling history as a resource actually sounds like a good idea for the very > reason that you want to see history in a bunch of different ways. You can > use the content-negotiation features of HTTP to specify to the history > resource exactly how you would like to view it. Puzzlement: why would you want to do content negotiation on version history? It's just data; how it gets viewed is up to the user agent. The history property attributes were being used to decrease the amount of history data that was being sent to the client. So I believe by "how you would like to view it", Yaron was referring to "how you would like to control what subset of the data you actually get sent". Cheers, Geoff
Received on Sunday, 23 May 1999 23:21:57 UTC