Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3AAA510602 for ; Tue, 6 Aug 2013 14:48:01 +0000 (UTC) Received: (qmail 99953 invoked by uid 500); 6 Aug 2013 14:47:57 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 99366 invoked by uid 500); 6 Aug 2013 14:47:57 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 99307 invoked by uid 99); 6 Aug 2013 14:47:56 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 14:47:56 +0000 Received: from localhost (HELO s2laptop.home) (127.0.0.1) (smtp-auth username markt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 14:47:56 +0000 Message-ID: <52010C9B.0@apache.org> Date: Tue, 06 Aug 2013 16:47:55 +0200 From: Mark Thomas User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Is the current Tomcat 7 servlet websocket implementation being deprecated? References: <2acf9b8a99ab446898682e4ae3613675@BLUPR06MB193.namprd06.prod.outlook.com> <5200ACCB.1090607@apache.org> <3fdc730623904be4a1dc7842534e3fb6@BLUPR06MB193.namprd06.prod.outlook.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 06/08/2013 16:00, Bob DeRemer wrote: > FINAL QUESTION on this thread: > > * with the understanding that the existing Tomcat 7 logic is being > deprecated, I have to ask: could/should it be used in production - > specifically if we know we're going to be expecting it to handle 50K+ > concurrent connections? Could it? Yes. Should it? I'd wait for the JSR-356 if at all possible. To be perfectly honest I'd start using 8.0.0-RC1. But I say that knowing that as a Tomcat committer, if I hit a problem that I need fixed I can commit the fix just as soon as I work out what it is :) If you are prepared to accept that there are likely to be some bugs and it might take us a couple of days (might be quicker) to get them fixed then I would go with 8.0.x. The upside for you is that any bugs you find should get fixed pretty quickly and once they have been fixed you'll have your application running on the latest release with the maximum lifetime with respect to long term support. For an idea of how quickly things get fixed, take a look at the dev list over the last few days as folks have been reporting problems with 8.0.0-RC1. If you opt to go the 8.0.x route, I'd encourage you to build form source (it is really simple) so you can pick up any fixes as soon as they are made. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org