tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Bergsten <h...@gefionsoftware.com>
Subject Re: [LONG TERM PLAN] Proposed Architecture for Tomcat.Next Servlet Container
Date Mon, 10 Jan 2000 18:24:24 GMT
Stefano Mazzocchi wrote:
> 
> Hans Bergsten wrote:
> 
> > > > Questions
> > > > ---------
> > > > A couple of questions that I have not seen any discussion about yet are:
> > > >
> > > > * Why are Request/Response representations of HttpServletRequest/Response
> > > >   instead of ServletRequest/Response?
> > > >
> > >
> > > It's based on my feeling that Tomcat is, first and foremost, an *HTTP* servlet
> > > container.  Most of the design energy and features focus is around things that
only
> > > matter when the container knows the contents of the HTTP headers.
> > >
> > > It would be reasonable to build a servlet engine for non-interactive, non-HTTP-based
> > > request/response stuff, but I don't see a lot of value add for doing this versus
> > > alternative solutions based on RMI and/or CORBA APIs.
> >
> > I was thinking about things like WebDAV, and possibly WAP. I imagine a server
> > for these protocols may need other ServletRequest/Response subclasses than
> > HttpServletRequest/Response.
> 
> [...]
> Anyway, you are thinking about WAP, but this doesn't matter. WAP is
> designed not to require changes in the http servers. WAP gateways are
> reponsible to provide WML encoding over digital wireless protocols to
> reduce bandwith, but as far as we are concerned, a WAP request is
> totally equivalent to an HTTP one (but, for example, for the user agent
> or other header identifier)
> 
> WebDAV? same thing. WebDAV is a "blown up" HTTP. Sure, we could add a
> WebDAVServlet, but that would extend HttpServlet in the real sense: it
> adds functionality over HTTP, but doesn't require any change down below
> in the middleware.

Okay, if both WAP and WebDAV are true supersets of HTTP (I take your word
for it), then using HttpServletRequest/Response here seems to be okay, since
WebDAVRequest/Response can then be subclasses to HttpServletRequest/Response.

Hans
-- 
Hans Bergsten		hans@gefionsoftware.com
Gefion Software		http://www.gefionsoftware.com

Mime
View raw message