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 (asf.osuosl.org: local policy)
Message-ID: <446A0785.40905@apache.org>
Date: Tue, 16 May 2006 19:10:29 +0200
From: Remy Maucherat <remm@apache.org>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Ongoing stuff
References: <4469A28F.9010703@apache.org>
 <96e4b5230605160806n2a4a01fbqe84915846e665aa1@mail.gmail.com>
In-Reply-To: <96e4b5230605160806n2a4a01fbqe84915846e665aa1@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Costin Manolache wrote:
> For those of us who don't know much about 'comet' - could you explain a bit
> more ?
> A small example, some pointers to what APIs are needed ( if it's not 
> service
> ),
> why service doesn't work, etc.

There's some documentation here: 
http://alex.dojotoolkit.org/wp-content/LowLatencyData.pdf

The (only) actually useful capability is of course to push back data at 
any time. To replicate the same with regular servlets, you need a 
forever running service method, which doesn't work that well. It's 
really evil-hype-powered stuff, and I think it's all your company's fault :(

However, since my attempts at SIP (which has the same biderectional 
capabilities without the hacks, of course) miserably failed, and since 
it's not too hard to implement in the APR connectors, I think it should 
be done (the API right now is an interface that the servlet should 
implement, but I plan to provide a ready to use abstract servlet which 
should be easy to work with).

Rémy

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