<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 5/22/14 10:54 AM, Tom Zeller wrote:</div>
<blockquote
cite="mid:CAMNmQDTZh2jXMbBk-CLvdwgP4K6So7_ocC7VP=ZEO32XJBDAag@mail.gmail.com"
type="cite">
<pre wrap="">
I am okay with targeting Servlet 3.0 for IdP 3.0, but I guess that
ties us to Jetty 9.0, and development is happening on the 9.1 and 9.2
branches, so I was a little less excited about that. I don't really
know as much regarding Tomcat development.
</pre>
</blockquote>
<br>
<br>
That's the part that that I'm not clear on. I don't have much
experience with Jetty. Does Jetty 9.1/9.2 *require* the app the be
written to the servlet 3.1 spec? That would sound atypical to me.
At least in my previous experience, you can deploy an app which
assumes and is written to servlet version X in a container which
supports version X or greater. Or put another way, you can deploy
an app written to an earlier servlet version from what a container
supports. But of course you won't be able to use any of the newer
servlet stuff in your app. For example, if the app is written to
2.5, you obviously can't use the 3.0 async stuff.<br>
<br>
I'm pretty certain that you can for example deploy a 2.5 app in
Tomcat 7 (which supports servlet 3.0). I would assume/hope that
one can deploy a 3.0 app in Jetty 9.1/9.2, unless there's just
something weird about Jetty. But I don't think you can do the
opposite (deploy a 3.1 app in a 3.0 container), so that's why I
mentioned it. If we don't actually need servlet 3.1, then we're
unnecessarily limiting the containers people can deploy in.<br>
<br>
On the other hand, if there are 3.1 features we want to use, then
that's another story entirely.<br>
<br>
<br>
<br>
</body>
</html>