users@grizzly.java.net

Re: Grizzly ROADMAP: 1.9.x and 2.0 -> Time to speak!

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Fri, 09 Oct 2009 10:20:05 -0400

Salut,

Oleksiy Stashok wrote:
> Hi,
>
>> (1) Grizzly 2.0 FCS, with a back to back white paper as a
>> pre-requisite for release. I sign up for the white paper :-)
> Ok :)
>
>>
>> (2) Forward port all the http/http-servlet-XX/Comet/OSGi works to
>> Grizzly 2.0
>>
>> ** Anybody interested to contribute I will give committer privileges
>> for free :-) **
>>
>>
>> Now I would like to vote on the following topic:
>>
>> 1. Should the Servlet Container works be only on top of 2.0? Or should
>> we make sure both version are supported?
> I think it depends on resources we have. Theoretically ServletContainer
> will use just high-level HTTP module API, so we will be able to use the
> same implementation for both versions.

Assuming we keep the (3) -> 1.9.x API.


>
>> 2. Should 1.9.19 be *our last* 1.9.x release with new features, and
>> then we move to sustaining mode?
> IMO yes.

Great!

>
>> 3. Should we refactor *entirely* the http module API and make sure it
>> is aligned with Grizzly 2.0 new design? I'm tempted to refactor
>> everything but we will break a lot of applications
> Probably we will need some refactoring to separate HTTP API classes from
> HTTP server logic, to make HTTP related classes usable for server and
> client sides.

Yes this is really something I would like to do. I also want the We
Framework to be more Google Guice (and Spring) friendly. We should
re-think the GWS API.


>
>> 4. Gitub or Kenai? For sure we MUST move out of java.net
> +1
> BTW, the bigger concern for me is maven repository. Jave.net maven
> repository is very slow and unreliable, do we have better choice?

I think we an upload to ibiblio directly.


> Glassfish maven repository?

That's a solution as well.

>
>> 5. Should we drop Cometd support? Cometd.org can be run using Grizzly
>> Comet + Atmosphere
> I have no opinion here. If we have Atmosphere as better solution - then,
> IMO, there is no reason to keep cometd.

We haven't followed the spec closely enough and right now our
implementation is out of date. Atmosphere already support the latest
Cometd version (1.0.0rc0), and that version runs on top of Grizzly Comet.

Thanks

-- Jeanfrancois


>
> WBR,
> Alexey.
>
>
>> If you can reply publicly, please reply to jfarcand_at_apache.org with
>> your request/recommendation.
>>
>> Please share your vision :-)
>>
>> A+
>>
>> -- Jeanfrancois
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>