18.07.2001 09:54:27, Christopher Lenz <[EMAIL PROTECTED]> wrote:
>should I make a simpler patch that let's you disable directory
>browsing but doesn't move the directory browsing functionality in a
>new class ? I'd really like to see this functionality in the basic
>slide servlet (i.e. without having to create my own WebdavServlet and
>GetMethod subclasses).
Okay, I'm now working on an alternative design that might be a lot
cleaner, so that:
- directory browsing can be disabled for the WebdavServlet and
- subclasses of WebdavServlet can easily implement custom handling
of requests on collections, without having to subclass GetMethod
*and* WebdavServlet, and maybe even PostMethod.
In my project, I'm trying to use the Slide WebdavServlet for handling
WebDAV communication, but extend the servlet to provide a custom look
and functionality for the collection html-pages, using a JSP-taglib to
display the directory contents, properties etc. I think this is
something that other slide-based servlets might want, too.
So, I'd like to have the GetMethod class 'dispatch' GET requests on
collections back to the servlets doGet() method (the standard
implementation of doGet() would be to return a FORBIDDEN response
code, or generate the standard directory-index). Similarly, POST
requests on collections should also be handled by the servlets doPost
() method. Both doGet() and doPost() would not get called when non-
collection resources are requested.
Does that make sense ?
-chris
________________________________________________________________
[EMAIL PROTECTED]
