Dave, Thanks for looking at the details on Directory implementation. This are certainly opportunities to refactor and optimize this class. As you found out, it is handling pretty complex stuff. We would welcome some contributions in this area. We have also received a report regarding performance issue of Directory used with the WAR client that we need to inspect. This might be due to the same reason: "Improve performance of WAR client" http://restlet.tigris.org/issues/show_bug.cgi?id=736 Regarding the production ready status, we have been using this class on all our Web sites with no trouble so far. Would you mind creating a bug report for what you found? Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ <http://www.restlet.org/> http://www.restlet.org Noelios Technologies ~ Co-founder ~ <http://www.noelios.com/> http://www.noelios.com
_____ De : Rob Heittman [mailto:rob.heitt...@solertium.com] Envoyé : mardi 7 avril 2009 14:26 À : discuss@restlet.tigris.org Objet : Re: DirectoryResource throws/logs useless exceptions for CLAP protocol I also wish it were a bit faster. We do serve several hundred thousand impressions out of Directory every month, but we serve several million using thinner Resources not wrapped in Directory -- not sure what would happen if we wrapped those in Directory. On Tue, Apr 7, 2009 at 1:58 AM, David Fogel <carrotsa...@gmail.com> wrote: The Directory class is the only built-in way for plain, non-servlet, Restlet apps to serve static content. Should we consider it "production"-ready w.r.t. performance under load? Another way of asking this: is the Directory class a reasonable substitute for, e.g. Jetty's DefaultServlet? ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1593889
