The most important feature IMO is async servlets, which is used by Atmosphere. It allows you to suspend requests without relying on container specific implementations, like continuations in Jetty. Currently the atmosphere example, part of wicket-examples in sandbox/atmosphere uses the async attribute. Without it, it will probably work on most containers, but only because Atmosphere detects the container and has modules for most popular containers.
I can live with Servlet 2.5, but I don't see why we should keep supporting these ancient API's. I'd like to move on. On Friday 13 April 2012 21:37:22 Johan Compagner wrote: > Explain to me then what Wicket it self really needs from the new API? > > So what are we going to change? > On Apr 13, 2012 2:32 PM, "Emond Papegaaij" <emond.papega...@topicus.nl> > > wrote: > > Hi all, > > > > It was already mentioned by Martijn some time ago as a suggestion for the > > roadmap for Wicket 6, but it was never decided. The question is: should we > > move to servlet-api 3.0 or stay at 2.5. Servlet 3.0 has been around for > > over 2 > > years now and is supported by most (all?) servlet containers. It allows us > > to > > use things like the new annotations and asynchronous servlets. > > > > I'm +1 for moving to servlet 3.0 and already have some work done on the > > sandbox/atmosphere branch to get it working. > > > > Best regards, > > Emond
