Tobias Bocanegra wrote:
>>> I do not think, that this is a good idea. It involves magic and leaves
>>> the microsling context in a way we cannot and most probably will not
>>> support in Sling and thus creates an incompatibility.
>>>
>>> Rather I would suggest to implement a SpoolServlet (extends
>>> SlingSafeMethodsServlet) which handles nt:file requests
>>> (MicroSlingServlet.addServlet("nt:file", new SpoolServlet()) and just
>>> pumps out the nt:file (or the Property value to which the
>>> Node.getPrimaryItem() trail leads).
>> i agree with felix that having a spool servlet is a better option.
>> nevertheless, i would provide a webdav servlet with the default setup.
>> so that users can easily upload/manager their static content in the
>> repository.
>
> i rethought about this. the current webdav servlet in jackrabbit is
> pretty cool and feature complete. especially for GET requests it
> suports etags, if-last-modified-since, etc. and it would silly to
> reimplement this again.
>
> furthermore, i think for the other methods (PUT, DELETE, MKCOL) etc
> the webdav servlet provides the good defaults. so i suggest to drop
> the StreamServlet idea, and map all exact-match resources per default
> to the webdav servlet.
>
Perhaps I'm thinking too complicated here, but does this always work?
What about if I have
/content/test
/content/test.html
in my repository and try to get /content/test.html ?
This will be forwarded to the webdav servlet and I don't have any chance
to get the html view of /content/test.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
