[prev in list] [next in list] [prev in thread] [next in thread] 

List:       slide-dev
Subject:    Re: resourcetype: collection
From:       "Remy Maucherat" <remm () apache ! org>
Date:       2001-06-21 21:35:23
[Download RAW message or body]

> 21.06.2001 04:01:12, "Remy Maucherat" <remm@apache.org> wrote:
>
> >> hi everyone,
> >>
> >> some questions:
> >>
> >> when using the JDBCDescriptorsStore, why doesn't every collection
> >> (created from the domain-config) have the resourcetype-property
> >> set to "<collection/>" in the database ?
> >>
> >> I've seen that the first criteria to determine whether a resource
> >> is a collection would be when it has no revisions...
> >>
> >> if that is true, why is the collection-resourcetype stored at
> >> all, and not dynamically generated for every object without
> >> revisions ?
> >>
> >> [and on a somewhat more theoretical side, why is there obvious
> >> differentiation between collection-resources and normal resources
> >> in the slide-api ?]
> >>
> >> that should read "... why is there _no_ obvious differentiation
> >> ...". sorry.
> >
> >It's true that there are no obvious differences between resources and
> >collections in Slide, since a node can both have children and have
> content
> >at the same time.
> >
> >There is nothing there which goes against the WebDAV specification.
>
> well, not totally. but as far as I understand the RFC, PUT on
> collections is not allowed (conflict), but the spec is a bit vague at
> that point. in that case, if a slide node had content and children,
> you wouldn't be able to modify the content via WebDAV...

Actually, no.
8.7.2 just says it's undefined, and up to the server to decide.
Conflict is returned when there is no appropriate parent collection.

It doesn't indicate that I think it's a good idea to allow this. The current
WebDAV servlet actually disallows PUT on collections.

Remy

[prev in list] [next in list] [prev in thread] [next in thread]