Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Ongoing stuff
Date: Tue, 16 May 2006 07:17:54 -0400
Message-ID: 
 <F857E188F4D2794BAE94ED1ADB265EAD4B8711@MAIL02.bedford.progress.com>
Thread-Topic: Ongoing stuff
Thread-Index: AcZ4z4aChjeEuXLZT7iSzWs18Eu4IQACqhZQ
From: "Kevin A. Palfreyman" <kap@progress.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>

Remy,
This sounds interesting, but can I ask how this differs from what=20
Pushlets does using standard servlets? (http://www.pushlets.com/)  We=20
use these extensively, so obviously something that provides similar=20
functionality but with a lighter-weight backend might be interesting,=20
but I'd love to hear your views.

Also, would what you propose cause Tomcat lock-in for client code?

Thanks,

Kev=20

> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]=20
> Sent: 16 May 2006 11:00
> To: Tomcat Developers List
> Subject: Ongoing stuff
>=20
> Hi,
>=20
> I am proposing to add a new feature in the development branch=20
> to support=20
> comet (aka, being able to push data on a HTTP connection,=20
> outside of the=20
> execution of the service method of the servlet). Certain applications=20
> require this sort of capability (like gtalk; to be honest, I=20
> don't know=20
> that many apps which need it) and since usage of the HTTP (or AJP)=20
> connector is exclusive, it is not possible to really=20
> implement this sort=20
> of thing with Servlets. I would have liked to use SIP and SIP=20
> Servlets=20
> for this usage, but it looks like it's not going to happen.=20
> The feature=20
> will require APR to work in the intended way, but the wrapper servlet=20
> that I will use to present the functionality to the user should work=20
> with the regular java.io connectors (using a thread per=20
> connection, of=20
> course). In some ways, it is a bit similar to the sendfile=20
> addition, so=20
> it's probably useful, but proprietary.
>=20
> I will then:
> - do some spring cleaning in the code (externalizing=20
> hardcoded strings, etc)
> - try to lower the memory usage of a processor
>=20
> R=E9my
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>=20
>=20

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