hi christian, it's already scheduled for later (see [1]).
regards, gerhard [1] https://issues.apache.org/jira/browse/DELTASPIKE-349 2013/8/17 Christian Kaltepoth <[email protected]> > Hey all, > > I just realized that there is one thing left for the servlet module to > discuss. > > We agreed that it should be possible to disable the lifecycle events fired > for the request, response and session because it could lead to performance > problems in certain situations. > > Currently the module uses different listeners and filters for each event > type. Because of this, I think it would be a great usecase for the > Deactivatable feature of DeltaSpike, which we already use in other places. > This way users can disable events simply by deactivating the corresponding > listener or filter. > > In our discussion back then there was an idea of dynamically registering > the listeners/filters during startup if we find observers for the specific > events. IMHO this is an interesting idea, especially because this type of > dynamic configuration would be great for other stuff too. Especially for > the @WindowScope feature. But I think we will need more time to work on > this. Therefore I think we should use Deactivatable for now and schedule > the dynamic configuration for later. Of cause we can keep the > Deactivatable checks > in the filters/listeners even if we add the dynamic configuration on top of > it later. So we won't need to "change" anything in the future that may lead > to compatibility/migration issues. > > WDYT? > > Christian > > > -- > Christian Kaltepoth > Blog: http://blog.kaltepoth.de/ > Twitter: http://twitter.com/chkal > GitHub: https://github.com/chkal >
