<< However, from an abstract point of view, multiple URIs can identify the same resource even if they live on separate HTTP servers. In particular, the implementations wouldn't even know about the "other" URI, and it would be impossible require both servers to return the same DAV:resourceid. >> I believe you're talking about inter-server bindings. Because of garbage collection issues, I suspect the server that actually holds the resource will know about all bindings to the resource. But more importantly, I suspect all servers that bind to that resource will get the resourceid from the server that actually contains the resource just as they'd get other properties like the last modification date. Did you have something else in mind? I believe the resources should have a resourceid, but right now I can live with a proposal that lacks it. ------------------------------------------ Phone: 914-784-7569Received on Thursday, 1 August 2002 13:06:47 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:01 GMT