Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Subject: Re: [comet] state of the implementation
From: Remy Maucherat <remm@apache.org>
To: Tomcat Developers List <dev@tomcat.apache.org>
In-Reply-To: <71235db40901191450g7a7fa5cctedd43a813ef1f0b1@mail.gmail.com>
References: <71235db40901191450g7a7fa5cctedd43a813ef1f0b1@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Date: Tue, 20 Jan 2009 00:36:36 +0100
Message-Id: <1232408196.3041.16.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

On Mon, 2009-01-19 at 14:50 -0800, Matthias Wessendorf wrote:
> hi,
> 
> looking at the tomcat comet module [1] and comparing it to the one in
> jetty/dojo [2],
> I wonder if the package (api-part) in tomcat shouldn't be named
> "org.cometd" (-> [3]).
> 
> Another question is, is the tomcat module up-to-date? Since I see some diffs on
> the classes etc? (-> API)
> 
> Are there some thoughts of a more common module for this? Like working
> on the API
> with Jetty/dojo and just *reuse* the API, here in Tomcat and just care
> about the actual
> IMPL ?

This has been discussed one month ago. To summarize, this stuff is not a
standard, so something in the org.apache namespace was used.

BTW, this Tomcat cometd API is also available in JBoss AS 5, so that
should mean good production deployment availability (eventually).

Rémy


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org