Salut,
Jeanfrancois Arcand wrote:
> Salut,
>
> I would like to propose a change to the current Grizzly 2.0 way of using
> Future. Instead of having:
>
> IOFuture
> ConnectFuture
> ReadFuture
> WriteFuture
>
> I would like to align with the API and remove the above classes and
> instead add something like GrizzlyFuture. Looking at the code, the
> specialized API added to the above classes can be replaced with
I must have said that GrizzlyFuture is out implementation of the Future
interface and not exposed to the users/framework.
A+
-- jeanfrancois
>
> public R get() // Instead of getResults, which return the same as get
> anyway.
>
> Same for getImmediateReadResult, getImmediateWriteResult, etc. which can
> anyway get retrieved using Future.get().
>
> The ConnectFuture doesn't add any API as well, which I found strange.
>
> What do you think?
>
> A+
>
> -- Jeanfrancois
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>