It gets even a bit more complicated. In Jetty 7, the API's have been changed
to be "servlet 3 like", but not really servlet 3. Anyway, I have the
continuations working on the branch, but a lot of unrelated system tests are
failing and a bunch of the http-jetty unit tests are failing due to m
On Thursday 15 July 2010 9:53:28 pm Benson Margulies wrote:
> The continuation code is very different. I attached a first pass
> patch. It does not pass unit tests because I am completely flummoxed
> by mock, and I may not understand what's going on with the
> continuations.
Digging into this a bi
The continuation code is very different. I attached a first pass
patch. It does not pass unit tests because I am completely flummoxed
by mock, and I may not understand what's going on with the
continuations.
On Thu, Jul 15, 2010 at 9:13 PM, Willem Jiang wrote:
> Daniel Kulp wrote:
>>
>> On Thursd
Daniel Kulp wrote:
On Thursday 15 July 2010 2:33:26 pm Benson Margulies wrote:
The first part of the JIRA I filed above is easy: make a new project that
depends on jetty 7 instead of 6.
I'm somewhat rusty after that. A profile in systests to use it? Where is
the default transport established (w
On Thursday 15 July 2010 2:33:26 pm Benson Margulies wrote:
> The first part of the JIRA I filed above is easy: make a new project that
> depends on jetty 7 instead of 6.
>
> I'm somewhat rusty after that. A profile in systests to use it? Where is
> the default transport established (which I don't
The first part of the JIRA I filed above is easy: make a new project that
depends on jetty 7 instead of 6.
I'm somewhat rusty after that. A profile in systests to use it? Where is the
default transport established (which I don't propose to change) but what
else is called for?
