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 C484610ECD for ; Fri, 2 Aug 2013 18:00:10 +0000 (UTC) Received: (qmail 61182 invoked by uid 500); 2 Aug 2013 18:00:06 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 61134 invoked by uid 500); 2 Aug 2013 18:00:05 -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 61123 invoked by uid 99); 2 Aug 2013 18:00:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 18:00:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of igor.urisman@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vb0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 17:59:59 +0000 Received: by mail-vb0-f47.google.com with SMTP id h10so918343vbh.20 for ; Fri, 02 Aug 2013 10:59:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/qltmL+lJ6W4Tvl82q8srIHw7FH4wuTF9xKIv5ujyfI=; b=ycCeR11ro7L915g5zRn7FQ+eK4AV1swPhzUofg3qATw6zURJJlL/Ku4ZNYwygFN8Uf tAoaI+CzX2na9ULCNEHV23LS0ueubldp8SQA9hUJPIbNp2oVTYfgUgmmT3OIBhGmAEVR oV9qr5mdPjeEGYujcNcopxpgpbLbhoFoqWEVDShUBhviDABLzo+RFmPBWuaiL3QhZ4J/ Ki5m2oZN3LwHy7VTj5KGSFPCht51DuqqbuV5JM0v3dCeTCh5OXtJoZXvtvO8ZsBRrKEe ipj9CzC3trOYLk66QjOy80hjhPz7fFI/fheo+rARVyzGga7McMhggoH1/WVjyY41ZnDW ZmvQ== MIME-Version: 1.0 X-Received: by 10.52.53.5 with SMTP id x5mr1983396vdo.101.1375466378400; Fri, 02 Aug 2013 10:59:38 -0700 (PDT) Received: by 10.59.12.74 with HTTP; Fri, 2 Aug 2013 10:59:38 -0700 (PDT) In-Reply-To: <233713D9-29F2-4D45-80EB-A5A04FC05A9C@nicholaswilliams.net> References: <233713D9-29F2-4D45-80EB-A5A04FC05A9C@nicholaswilliams.net> Date: Fri, 2 Aug 2013 10:59:38 -0700 Message-ID: Subject: Re: Tomcat Websocket Implementation From: Igor Urisman To: Tomcat Users List Content-Type: multipart/alternative; boundary=089e01160864e297e804e2fab81f X-Virus-Checked: Checked by ClamAV on apache.org --089e01160864e297e804e2fab81f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Super helpful -- thanks, Nick. I'll switch to T8 right away. It's alpha status is not a problem in my case. -Igor. On Fri, Aug 2, 2013 at 10:45 AM, Nick Williams < nicholas@nicholaswilliams.net> wrote: > > On Aug 2, 2013, at 12:42 PM, Nick Williams wrote: > > > > > On Aug 2, 2013, at 12:05 PM, Igor Urisman wrote: > > > >> Dear all, > >> > >> I'm looking into a solution that will make extensive use of websockets= . > >> Details are unimportant, but here's the question that I'd like to have > some > >> insight into. The current implementation (official > >> example< > http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/examples/WEB-IN= F/classes/websocket/chat/ChatWebSocketServlet.java?revision=3D1354477&view= =3Dmarkup > >) > >> seems independent of the JSR > >> 356. > >> Is work underway to implement the javax.websocket.* objects, or is > what's > >> in org.apache.catalina.websocket it for the enforceable future? > > > > Tomcat 8 has a completed (though not yet fully tested and vetted) > implementation of JSR-356. We're voting right now on the developer's > mailing list whether to release Tomcat 8.0.0-RC1 alpha. > > > > Though Tomcat 8 is the only Tomcat that will support the Servlet, JSP, > and EL specifications included in Java EE 7 (they will not be back-ported > to Tomcat 7), a decision was made a while ago to deprecate the existing > Tomcat 7 WebSocket implementation and back-port JSR-356 to Tomcat 7. This > is the only Java EE 7 component that will be back-ported to Tomcat 7, > AFAIK. I don't personally know this will happen (I'm not one of the > developers), but since the JSR-356 implementation in Tomcat 8 is complete > now, it shouldn't be too long. > > **I don't personally know WHEN this will happen=E2=80=A6 > > > > > If you want to play with the JSR-356 implementation for now, feel free > to download and use Tomcat 8 RC1 when it releases in (hopefully) the next > few days. We encourage it, because the more people who download it and tr= y > it out, the better our chances of chasing down and fixing bugs now instea= d > of after a general release. > > You could also download the POTENTIAL release candidate that is being > voted on right now ( > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.0-RC1/bin/), > but I can't guarantee that this is the actual release candidate that will > come out. > > > > > Nick > --089e01160864e297e804e2fab81f--