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 (athena.apache.org: domain of costin@gmail.com designates
 209.85.161.173 as permitted sender)
Received-SPF: pass (google.com: domain of costin@gmail.com designates
 10.60.28.168 as permitted sender) client-ip=10.60.28.168;
MIME-Version: 1.0
In-Reply-To: <4F3D7F02.4020208@apache.org>
References: 
 <CAP8-FqnAxDepNtpUzUuZCFMe3krmRBNsofaN2frkH_qTzrDyKw@mail.gmail.com>
	<1328177144.1943.4.camel@mail.remm.hd.free.fr>
	<4F2A7478.1070905@apache.org>
	<CAP8-FqnKwBEw+Jzb4Boi9SSk4bUQHu6hoeiFNVDbkTdwRvVg6A@mail.gmail.com>
	<4F2A9FC4.8060908@apache.org>
	<CAP8-Fqk+k9qECgFmaxAZDfo7O=ngu0xpxKsY-Mfx06W326m2Nw@mail.gmail.com>
	<4F3A9B82.6030605@apache.org>
	<CAP8-FqnakB6o=B2SzQUCdkCzeJoYfen8xhSVB9qitVpDQR7jng@mail.gmail.com>
	<4F3AEF17.2070708@apache.org>
	<CAP8-FqnqC3KoOqzPNy8FcvHi7C0m3bTabs=NucEJSm1c45hEhQ@mail.gmail.com>
	<4F3B6E0F.1090701@apache.org>
	<CAP8-Fq=ReBFp2iBEsTYVBHuGLJKzH1AjKyde1SoWdAMz0JT_ng@mail.gmail.com>
	<4F3BFA0A.6010203@apache.org>
	<CAP8-Fq=XfykgmdvLjRoRZS6pWKPYtCMrcqhMTe0gdfqAtCoaaA@mail.gmail.com>
	<4F3C1123.6090105@apache.org>
	<CAP8-FqkhwnweBxw_K_qREpbGJU1pj5a0-jTstOpWXYP_UbxS8Q@mail.gmail.com>
	<4F3D7F02.4020208@apache.org>
Date: Wed, 22 Feb 2012 08:51:52 -0800
Message-ID: 
 <CAP8-Fq=rp3u9c6K_muHQ1Ms8=j_HoBCqZc95a7cN+XNY-pgvqw@mail.gmail.com>
Subject: Re: SPDY support
From: Costin Manolache <costin@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=e89a8ff1c4e831550f04b99058ba

--e89a8ff1c4e831550f04b99058ba
Content-Type: text/plain; charset=UTF-8

First part submitted. For the second: what is the process for adding a
dependency ?

jzlib is BSD - I added it to 'download' and build.properties.
I can make it optional (i.e. skip building the code that depend on it if
jzlib is missing ), but it doesn't seem to be worth it.
Do automatic builders run 'ant download' ?

Any concerns with it ?

Costin

On Thu, Feb 16, 2012 at 2:11 PM, Mark Thomas <markt@apache.org> wrote:

> On 16/02/2012 01:44, Costin Manolache wrote:
> > That doesn't mean the application must receive the entire message as one
> > byte[]
> > or as a Stream.
> > You can have a very large fragment but still read it in smaller buffers
> and
> > notify
> > the user of message start and for each fragment ( I guess like xml
> parsing
> > ).
>
> I see where you are coming from now. A purely message based API would be
> possible in that case. The downside is increased complexity in the
> applications as they would have to maintain additional state across
> messages. I'm not completely against the approach, just not yet
> convinced that the trade is worth it. I'd prefer to have some hard
> evidence to work with but that is unlikely to be forthcoming until folks
> start using this API. With that in mind, I'm going to focus on the
> various contributions folks have made and move the implementation closer
> to something that is usable.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

--e89a8ff1c4e831550f04b99058ba--