Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 25412 invoked from network); 18 Dec 2008 22:02:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Dec 2008 22:02:03 -0000 Received: (qmail 48255 invoked by uid 500); 18 Dec 2008 22:02:12 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 48207 invoked by uid 500); 18 Dec 2008 22:02:12 -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 48196 invoked by uid 99); 18 Dec 2008 22:02:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2008 14:02:12 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.22.94.67] (HELO virtual.halosg.com) (72.22.94.67) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2008 22:01:50 +0000 Received: (qmail 19537 invoked from network); 18 Dec 2008 16:01:27 -0600 Received: from 72-19-171-38.static.mesanetworks.net (HELO ?192.168.3.131?) (72.19.171.38) by halosg.com with SMTP; 18 Dec 2008 16:01:27 -0600 Message-ID: <494AC836.9080608@hanik.com> Date: Thu, 18 Dec 2008 15:01:26 -0700 From: Filip Hanik - Dev Lists User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Bayeux/Cometd API question References: <20081218132543.19500@gmx.net> In-Reply-To: <20081218132543.19500@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Feel free to contribute any API changes you feel need to be added Filip fl-00@gmx.de wrote: > Hi together, > > I've developed a Bayeux/Cometd application using the Jetty implementation running in Tomcat 5. Development started several month back with no Tomcat Bayeux implementation available. > With this setup the application works well for limited traffic but of course not for high-volume traffic (since that way it can't really scale). I'm following the Tomcat Bayeux development for several months now. Currently, I'm somewhat concerned about the Bayeux-API differences between Jetty and Tomcat, and I can't see any sign/any attempt of unifying the API (this prevents us to switch to the Tomcat Bayeux implementation and we need to even think about switching completely to Jetty). > > I know that org.cometd.Bayeux is not a real standardized thing and it's being hosted at mortbay.org. But are there any plans for the Tomcat implementation to catch up with the latest (at least half-"official") API? Or even any vision of Tomcat/Jetty people pulling Bayeux/Cometd together towards a common direction/standardized API (or even JSR)? The current situation is somewhat unfortunate for a developer of a large Bayeux/Cometd application. > > Best Regards, > Florian > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org