Salut,
gustav trede wrote:
>
>
> 2008/10/14 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>>
>
> Salut,
>
>
> gustav trede wrote:
>
> THello,
>
> Continuation is initialized per default for all new comethandlers.
> What about the Streaming usage case, where continuation is not
> needed ?.
>
>
> OK I'm not sure I fully understand. By continuation, what are you
> meaning exactly? Grizzly Continuation might be what you are looking for:
> <https://grizzly.dev.java.net/nonav/apidocs/com/sun/grizzly/GrizzlyContinuation1x.html>
>
>
> never mind, i was confused, due to that i never need client based io to
> be handled after the initial connect i believed the continuation was
> something more complex when needed for the simple server -> client
> streaming usage case.
>
> So in that situation the only thing continuation does, is to keep the
> servlet from closing the connection and its data streams to the socket ?.
Yes.
>
> Or does the continuation logic also looks for interrupted, closed
> connections and forwards those events to comethandler ?.
No, just suspend/resume. This is an easy API to use, but with very
limited functionality. Actually it is build on top of Grizzly Comet
framework:
https://grizzly.dev.java.net/nonav/xref/com/sun/grizzly/GrizzlyContinuation1x.html#42
One CometContext per suspend/resume.
A+
-- Jeanfrancois
>
>
> regards
> gustav
>