Hi,
OK nothing formal, but here is what's missing before we can do the first
alpha release of 1.5 (1.5.1)
What need to be ported from :
Grizzly 1.0.11 to modules/grizzly/
-----------------------------------
+ SSL support (as an SSLProtocolFilter)
+ NIO blocking mode, both for SSL and clean (do we want such support?)
+ Round Robin OP_READ Selector pool.
+ Executor based Thread Pool (although we know it is slower than the
notify/wait)
+ Exception Handling
+ Logging
Grizzly 1.0.11 to modules/http/
-----------------------------------
+ Grizzly Web Server (moving ProcessorTask --> HTTPParserFilter)
+ Refactor SelectorThread to use the 1.5 framework
Grizzly 1.5.1
--------------
+ Need examples (we have several examples internally)
+ Need documentations and presentation.
+ Push all the documentation we did the last 6 months of Grizzly.next
(internally called v2). That will help deciding what Grizzly 2.0 will
looks like.
Once the Grizzly Web Server is fully functional, all the current
extensions (Grizzly Asynchronous Request Processing, comet, cometD,
etc.) will be easy to port with minimal changes. I would like to keep
the public interface unchanged to keep all existing users of Grizzly
1.0.x happy :-). I would like to keep those extensions outside the
"framework" for now (as other module) and decide later if we want to add
it to the framework or let them as extensions.
I will concentrate next week to port the WebServer. I know it is a
boring task to port from 1.0.11 to 1.5, but might be a good opportunity
to learn the code. Once I have the WebServer working, I will work on the
1.0.11 -> 1.5.
Now I would like to give a talk about the 1.5 design next meeting. That
should be a good start to help understanding 1.5.
Though?
Thanks
-- Jeanfrancois