ver 1 nov29, 2001 slide #1 webdav bindings property author: peter raymond

7
Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Upload: david-sweeney

Post on 27-Mar-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #1

WebDAV Bindings Property

Author: Peter Raymond

Page 2: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #2

Hierarchy

Resource R1 Resource R2

Root Collection

Bindings:

Coll1 Coll2 Coll3

Collection C1

Bindings:

Foo Bar

Collection C2

Bindings:

Foo

Page 3: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #3

Hierarchy

Resource R1 Resource R2

Root Collection

Bindings:

Coll1 Coll2 Coll3

Collection C1

Bindings:

Foo Bar

Collection C2

Bindings:

Foo

So R2 can be accessed as:

/Coll1/Bar

/Coll2/Bar

/Coll3/Foo

Page 4: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #4

Possible Interpretations

The definition of the bindings property is really misleading, I can think of three possible implementations of that property:

•The bindings property contains all possible hrefs and segment names for the resource.

•The bindings property contains all possible segment names but only one href per collection.

•The bindings property only contains the bindings given the parent collection of the PROPFIND request.

I now think that option 2 (only one href for the collection) is the correct definition!

Page 5: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #5

All possible URIs

The definition of the bindings property states that it contains “a complete list of all bindings to that resource”. So “complete” would imply all possible URI paths that could be used to access that resource.

Resource R1 Resource R2

Root Collection

Bindings:

Coll1 Coll2 Coll3

Collection C1

Bindings:

Foo Bar

Collection C2

Bindings:

Foo

PROPFIND /Coll2/Bar will return:

<bindings>

<href>/Coll2/</href>

<segment>Bar</segment>

<href>/Coll1/</href>

<segment>Bar</segment>

<href>/Coll3/</href>

<segment>Foo</segment>

</bindings>

Page 6: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #6

Only one URI for the collection

The definition of the bindings property states that “it is necessary to select one URI mapping for the collection”. So this seems to imply that if a collection has a binding to this resource but that collection itself has multiple bindings to it then you must pick one URI for that collection (preferably the one used when the resource was bound into the collection).

Resource R1 Resource R2

Root Collection

Bindings:

Coll1 Coll2 Coll3

Collection C1

Bindings:

Foo Bar

Collection C2

Bindings:

Foo

PROPFIND /Coll2/Bar will return:

<bindings>

<href>/Coll2/</href>

<segment>Bar</segment>

<href>/Coll3/</href>

<segment>Foo</segment>

</bindings>

Page 7: Ver 1 Nov29, 2001 Slide #1 WebDAV Bindings Property Author: Peter Raymond

Ver 1 Nov29, 2001 Slide #7

Only one collection

The definition of the bindings property states that “it is necessary to select one URI mapping for the collection”. So this might imply that the property only contains one href (for the collection containing the resource), perhaps from the BIND or PROPFIND request?.

Resource R1 Resource R2

Root Collection

Bindings:

Coll1 Coll2 Coll3

Collection C1

Bindings:

Foo Bar

Collection C2

Bindings:

Foo

PROPFIND /Coll2/Bar will return:

<bindings>

<href>/Coll2/</href>

<segment>Bar</segment>

</bindings>