• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • core

      This issue is a trial balloon to see how people think of us moving to Servlet 3.0 as the minimum requirement for Jenkins to improve user experience.

      If you have thoughts about this (including arguments against this), please make your case as a comment, so that we can make an informed decision.

          [JENKINS-23378] Raise minimum requirement to servlet 3.1

          Kohsuke Kawaguchi created issue -

          Kohsuke Kawaguchi added a comment - See http://jenkins-ci.org/content/thinking-about-moving-servlet-30 for the context.

          I think this is fine and we should just go on with this.
          If someone has an issue with this, then he does not have to update to the latest version until he is ready.

          In general I think the level of compatibility we try to fulfil with jenkins is not healthy for the project anymore...

          Dominik Bartholdi added a comment - I think this is fine and we should just go on with this. If someone has an issue with this, then he does not have to update to the latest version until he is ready. In general I think the level of compatibility we try to fulfil with jenkins is not healthy for the project anymore...

          rsandell added a comment -

          I've been trying to get the support guys to upgrade our Jenkins env to tomcat7 for a while now, but we keep backing down to tomcat6 as soon as instabilities arise.
          So I'm for this change as it would force us to actually take the leap

          rsandell added a comment - I've been trying to get the support guys to upgrade our Jenkins env to tomcat7 for a while now, but we keep backing down to tomcat6 as soon as instabilities arise. So I'm for this change as it would force us to actually take the leap

          +1 for the Switch. Guys using tomcat6 should be able to move to tomcat7.

          Conny Kreyßel added a comment - +1 for the Switch. Guys using tomcat6 should be able to move to tomcat7.

          Upgrading to Servlet 3.0 is a great idea, especially if only the 3% user base will be impacted.

          The only thing to have in consideration is that without servlet 3.1 Jenkins won't be able to use WebSockets or Server-Side Events, as both require non-blocking IO and HTTP protocol upgrade, features available from Servlet 3.1.

          All the libraries that I know that promise comet-style communication for Servlet < 3.1 use long polling, or open a special port for the WebSocket connection.

          Marcelo Rebasti added a comment - Upgrading to Servlet 3.0 is a great idea, especially if only the 3% user base will be impacted. The only thing to have in consideration is that without servlet 3.1 Jenkins won't be able to use WebSockets or Server-Side Events, as both require non-blocking IO and HTTP protocol upgrade, features available from Servlet 3.1. All the libraries that I know that promise comet-style communication for Servlet < 3.1 use long polling, or open a special port for the WebSocket connection.

          I'm changing this to Servlet 3.1. See this post for an overview of what's new in servlet 3.1. Among other things it support NIO.

          Kohsuke Kawaguchi added a comment - I'm changing this to Servlet 3.1. See this post for an overview of what's new in servlet 3.1. Among other things it support NIO.
          Kohsuke Kawaguchi made changes -
          Summary Original: Raise minimum requirement to servlet 3.0 New: Raise minimum requirement to servlet 3.1

          Daniel Beck added a comment -

          Tomcat 8 is the first release to support 3.1 (initial release mid 2014).

          Jetty 9.1 is required for 3.1, which will require updating Winstone-Jetty (which is based on 8.1 with Servlet 3.0 support only).

          WebSphere may only support Servlet 3.1 in its current 9 beta release?

          May be interesting to repeat the experience used to gather the data for the spreadsheet linked from http://jenkins-ci.org/content/thinking-about-moving-servlet-30 for Servlet 3.1. The spec is only two and a half years old, rather than 3.0's five when this issue was opened (now 6.5 years).

          Daniel Beck added a comment - Tomcat 8 is the first release to support 3.1 (initial release mid 2014). Jetty 9.1 is required for 3.1, which will require updating Winstone-Jetty (which is based on 8.1 with Servlet 3.0 support only). WebSphere may only support Servlet 3.1 in its current 9 beta release? May be interesting to repeat the experience used to gather the data for the spreadsheet linked from http://jenkins-ci.org/content/thinking-about-moving-servlet-30 for Servlet 3.1. The spec is only two and a half years old, rather than 3.0's five when this issue was opened (now 6.5 years).
          Patrick Wolf made changes -
          Labels New: 2.0

            Unassigned Unassigned
            kohsuke Kohsuke Kawaguchi
            Votes:
            7 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: