Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 87633D1D5 for ; Wed, 27 Jun 2012 19:50:11 +0000 (UTC) Received: (qmail 81645 invoked by uid 500); 27 Jun 2012 19:50:10 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 81575 invoked by uid 500); 27 Jun 2012 19:50:10 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 81565 invoked by uid 99); 27 Jun 2012 19:50:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 19:50:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [66.160.196.165] (HELO arizona.hanik.com) (66.160.196.165) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 19:50:01 +0000 Received: from workstation (184-96-227-85.hlrn.qwest.net [184.96.227.85]) by arizona.hanik.com (Postfix) with ESMTPSA id 38A94A8001D5 for ; Wed, 27 Jun 2012 13:45:41 -0600 (MDT) From: "Filip Hanik \(mailing lists\)" To: "'Tomcat Developers List'" References: <021301cd5499$51c09f00$f541dd00$@hanik.com> <4FEB603A.10002@apache.org> In-Reply-To: <4FEB603A.10002@apache.org> Subject: RE: Starting on 3.1 implementation Date: Wed, 27 Jun 2012 13:49:41 -0600 Message-ID: <022301cd549d$fed2d100$fc787300$@hanik.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIhOiWLulGVNhXUimTERKNOvTXhjQKv/evjllFHJZA= Content-Language: en-us > > 3.1 seems to be a fairly minor update so far, so we should be able to > start > > pushing Tomcat 8 right around the time as the spec is finalized. > > Just a word of caution. The EG is far from agreed on the best way to do > the non-blocking API at the moment. As with happened with the 3.0 async > API, a complete re-write could still happen. [Filip Hanik] That's ok. Non blocking can be done in many ways. As with the sandbox example, it was done without modifying streams, and still worked. So as long as the underlying implementation supports it, I don't suspect that an API change would change a lot in the belly of the beast. > > The EL EG has added a whole bunch of features. On the plus side the > updated jjt file is included in the spec that should speed things up a > fair bit. > > I haven't heard anything in terms of JSP updates. I can't imagine there > will be much there. > > My current focus on Tomcat 8 is re-factoring the resources to remove all > the JNDI stuff. After that, I'll probably look at the HTTP upgrade bit. [Filip Hanik] Interesting, what's up with JNDI, prolly something I missed from an earlier discussion? Filip --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org