yes there is some overhead. but it is much better then the servlet. the filter can let the resource fall through and be served by the servlet cotainer. if you use a servlet then the servlet itself has to stream the resource out. guess which will have a more optimized implementation...
-igor On Jan 11, 2008 5:33 PM, Maris Orbidans <[EMAIL PROTECTED]> wrote: > > > also wicket filter is much better at handling /* mapping > > > The only problem with this mapping is that filter is invoked for all > requests that fetch static web resources (css, images, etc). > I may be wrong but I don't think it's good for performance. Especially > if you use some other filter, for example, OpenEntityManagerInViewFilter > which opens a JPA session for each request. > > Maris > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
