tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rahul Saxena <rahul.saxena.cs...@itbhu.ac.in>
Subject Re: Feedback on my project proposal
Date Thu, 02 Apr 2009 14:58:51 GMT
It was a mistake I wrote "servlet context of this particular servlet " .

Also as we have default host for a particular engine , we can have a default
context for a particular host , then pass its servlet context to the filter
, then can we map all servlets in this host to this filter or the servlets
in this particular context only can be mapped ???

On Thu, Apr 2, 2009 at 3:55 PM, Mark Thomas <markt@apache.org> wrote:

> Rahul Saxena wrote:
> Could you clarify please? I don't understand your solution.
>
> > If we define a generic servlet for a particular host and then allow
> > servlets(of any application) in that particular host  to implement that
> > generic servlet
> Is "generic servlet" an interface? If so, we have no way of making any
> application servlet implement it.
>
> > and then I think we can supply the servlet context of this
> > particular servlet to the correponding filter of that host .....
>
> There is one ServletContext per web application. There isn't one
> ServletContext
> per Servlet.
>
> Mark
>
> >
> > On Wed, Apr 1, 2009 at 4:31 PM, Mark Thomas <markt@apache.org> wrote:
> >
> >> Rahul Saxena wrote:
> >>> I have posted my application on the GSOC site for the project "Convert
> >>> tomcat valves to filters" , Can anyone give their comment on the
> >> same.......
> >>
> >> Feedback provided in the GSOC app and repeated below. Feel free to
> discuss
> >> your
> >> ideas regarding these questions on the dev list.
> >>
> >> Mark
> >>
> >>
> >> Feedback:
> >> Good first draft. There are a couple of areas where I would like to see
> a
> >> little
> >> more information:
> >>
> >>   1. There are many more valves than the 6 you listed.
> >>   2. The filter requires a ServletContext at initialisation. How might
> you
> >> handle this for a filter defined at the Engine/Host level?
> >>   3. Authentication will require access to Tomcat internals. Is a filter
> >> the
> >> right solution for these valves? What might a better approach be? What
> >> about JSR
> >> 196?
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: dev-help@tomcat.apache.org
> >>
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>


-- 
Rahul Saxena
B.Tech Part III
Computer Science and Engineering
I.T. B.H.U. ,Varanasi
Contact No.-09452196645

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message