In my initial excitement of the idea, I got a little ahead of myself. I 
see where you are coming from now, and why you define the filters in the 
config file. The big problem with putting a filter in a sevlet is that 
that same servlet might not have been accessed based on it's own filter. 
But the filter wouldn't have been called if you never loaded the 
servlet. Catch-22.

However, I do think that there is value in being able to define a filter 
per-servlet. By this I mean that each sevlet could define behavior on 
it's own based on the path so far, with filters defined in 
Application.config serving as a default. Also, the filters could be 
processed down through the inheritance hierarchy. So the SitePage's 
filters would fire, then the MiddlePage's, and finally, assuming the 
filters allowed the request to get this far, the ChildPage's filter 
would be processed. But if I want that, maybe I should just use CherryPy 
;-). They have (IMHO) a nice URL parsing system that seems very similar 
to this (at least functionally).

I still like the idea of these filters in Webware (even if it's not 
"per-servlet").

--John
> I'm not sure if I fully understand this (and I'd like to).  What  
> would it mean for them to be per-servlet?  Would that mean that the  
> chain could depend on which servlet was actually called, rather than  
> on which filters matched the URL?
>
> One of the strengths of the way it works now is it's actually  
> important/useful to define behavior on the pattern of the URL.   
> That's sort of the big win.
>
> Or am I misunderstanding?  Could you talk out how you'd imagine using  
> it in a per-servlet manner?
>   

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Webware-devel mailing list
Webware-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to