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. -- /=============================================================\ |John Stracke | My opinions are my own | S/MIME & HTML OK | |francis@ecal.com|============================================| |Chief Scientist | NT's lack of reliability is only surpassed | |eCal Corp. | by its lack of scalability. -- John Kirch | \=============================================================/Received on Saturday, 22 May 1999 09:42:34 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:49 GMT