- From: Werner Donné <werner.donne@re.be>
- Date: Wed, 28 May 2008 21:01:20 +0200
- To: Jack Cleaver <jack@jackpot.uk.net>
- Cc: WebDAV <w3c-dist-auth@w3.org>
Indeed, you have to override the HttpServlet class in order to deal with the new methods, but I fail to see why that should be a problem. My concerns regarding an application server are: - that it complies with RFC 2616; - that it complies with the relevant J2EE specifications; - that it provides a robust infrastructure. Werner. On 28 May 2008, at 20:43, Jack Cleaver wrote: > > Julian Reschke wrote: >> Jack Cleaver wrote: >>> ... I found both Tomcat's and Jetty's HTTP stack to be unsuitable >>> as a basis for building a DAV stack. Certainly it *should* be as >>> you suggest; but these programs weren't designed with this kind of >>> extension in mind. Really, it is much easier to throw it all away >>> and start again. >>> Jetty is much better than Tomcat in this respect; but even Jetty >>> has some limitations. This isn't really criticism; designing >>> software to be extensible without having much of a clue what >>> extensions people are going to try and build is very difficult. ... >> Out of curiosity: what kinds of problems did you experience? > > As I recall, I couldn't override the built-in Tomcat HTTP method > handlers without overriding the HTTP servlet itself. > > This was over a year ago, and I haven't touched the code for a while. > > -- > Jack. -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: werner.donne@re.be
Received on Wednesday, 28 May 2008 19:02:01 UTC