RE: Restlet "Directory" suggestion
Hi Cliff, Ok, good idea for the XML representation. There is a related RFE that I've just updated: "Provide an XML directory listing representation" http://restlet.tigris.org/issues/show_bug.cgi?id=420 Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : Cliff Binstock [mailto:[EMAIL PROTECTED] Envoye : mercredi 26 novembre 2008 23:50 A : discuss@restlet.tigris.org Objet : RE: Restlet "Directory" suggestion Jerome, Inline ... > Thanks for the good feed-back on Directory. > > 1) Could you give more information/pointers? What do you want to transform > with XSLT, the directory listing? Yes, the directory listing. While quite obtuse, in Tomcat there is a built-in XML directory listing to which you can apply a stylesheet. Perhaps you could automatically return different variants? > 3) You could add a Guard filter in front of your Directory that would deal > with that, unless the authorization is based on the actual file. Could you > detail your use case a bit more? The basic guard isn't friendly enough. If I have users 'John', 'Fred', and 'Alice', I'd like to have /user/John; /user/Fred; /user/Alice. Each person has access only to their own directory (or perhaps some other complex authorization like groups). Cliff
RE: Restlet "Directory" suggestion
Jerome, Inline ... > Thanks for the good feed-back on Directory. > > 1) Could you give more information/pointers? What do you want to transform > with XSLT, the directory listing? Yes, the directory listing. While quite obtuse, in Tomcat there is a built-in XML directory listing to which you can apply a stylesheet. Perhaps you could automatically return different variants? > 3) You could add a Guard filter in front of your Directory that would deal > with that, unless the authorization is based on the actual file. Could you > detail your use case a bit more? The basic guard isn't friendly enough. If I have users 'John', 'Fred', and 'Alice', I'd like to have /user/John; /user/Fred; /user/Alice. Each person has access only to their own directory (or perhaps some other complex authorization like groups). Cliff
RE: Restlet "Directory" suggestion
Cliff, Thanks for the good feed-back on Directory. 1) Could you give more information/pointers? What do you want to transform with XSLT, the directory listing? 2) Good point. I've entered a RFE for this: "Directory listing should support XHTML" http://restlet.tigris.org/issues/show_bug.cgi?id=667 If you could provide a patch, that would be welcome. 3) You could add a Guard filter in front of your Directory that would deal with that, unless the authorization is based on the actual file. Could you detail your use case a bit more? 4) We have two pending RFEs for WebDAV in Restlet 1.2 "Add minimal support for WebDAV in Directory" http://restlet.tigris.org/issues/show_bug.cgi?id=346 "Add full WebDAV extension" http://restlet.tigris.org/issues/show_bug.cgi?id=519 However, we will have to start from scratch (+ contributions by Restlet community) as we don't want to introduce a dependency on Tomcat for this feature. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : Cliff Binstock [mailto:[EMAIL PROTECTED] Envoye : mardi 25 novembre 2008 18:16 A : discuss@restlet.tigris.org Objet : Restlet "Directory" suggestion Thierry, et al, I have been working with the "Directory" class, and running into limitations. I realized that because I am also running Tomcat, the built-in webdav met my needs. However--and because you were asking for suggestions--I realized that the Directory class could easily be improved: 1) Allow for stylesheets, see Tomcat's WebdavServlet setup (localXsltFile, and globalXsltFile). Note that a URI (instead of a path) would be even better. 2) Have the default representation return XHTML (instead of the current non X HTML). This would allow a programmatic caller to read the list as XML (a request from one of my users). 3) Add a simple authorization hook, or at least clearly describe how to authorize access to certain directories. Note that even in Tomcat, I had to go digging through the code to figure out how to subclass. 4) Add full webdav capability. Given that WebdavServlet is Apache License--and not very big--it seems that you could easily support full webdav out of the box. Cliff Binstock Coyote Reporting
Restlet "Directory" suggestion
Thierry, et al, I have been working with the "Directory" class, and running into limitations. I realized that because I am also running Tomcat, the built-in webdav met my needs. However--and because you were asking for suggestions--I realized that the Directory class could easily be improved: 1) Allow for stylesheets, see Tomcat's WebdavServlet setup (localXsltFile, and globalXsltFile). Note that a URI (instead of a path) would be even better. 2) Have the default representation return XHTML (instead of the current non X HTML). This would allow a programmatic caller to read the list as XML (a request from one of my users). 3) Add a simple authorization hook, or at least clearly describe how to authorize access to certain directories. Note that even in Tomcat, I had to go digging through the code to figure out how to subclass. 4) Add full webdav capability. Given that WebdavServlet is Apache License--and not very big--it seems that you could easily support full webdav out of the box. Cliff Binstock Coyote Reporting
