Spring 4 and Servlet 3.0

[Rod Widdowson]

In as much as I understand this,  going for 4 year old technology does seem
like a much better bet that going for the 8 year old one (but the 6 months
old one seems too new).

> my impression right now is that 3.0 is probably
> the one to target anyway, to avoid supporting people using badly out of
> date containers.

....Whilst at the cost of adding extra impedance to the upgrade path.  On
the other hand we are shipping a container (aren't we?) so for less advanced
user things should be easier rather than harder, notwithstanding the
required container change (they go from having to worry about Tomcat to not
worry about Jetty).  The advanced users shouldn't have so much of a problem.

This might also provide benefit to those poor souls trying to cram this into
WebSphere or other gnarly stuff.

We discussed last week what is happening to the REMOTE_USER interface and,
as I recall & understood, the upshot was that such Spring dictates that
handling needs to remain inside the container.  Does the combination of that
plus the upping of the container version add any new restrictions and if so
do we care?

The scenario I am imagination is interaction with another SSO system which
*cannot* run in Servlet3 but can in 2.5.  

Rod