Hi,
to improve the Grizzly HTTP module, I'm currently working on more high
level object than com.sun.grizzly.tcp.Request/Response called
GrizzlyRequest/GrizzlyResponse/GrizzlyReader/GrizzlyWriter which hide
all the complexity of the current API com.sun.grizzly.tcp (we got a lot
of questions on that topic). To make that happening, I would like to
move classes from the modules/http to modules/http-utils:
{A}
http/src/main/java/com/sun/grizzly/tcp/*
to
http-utils/src/main/java/com/sun/grizzly/tcp/
and
{B}
http/src/main/java/com/sun/grizzly/standalone/**Adapter.java
to
http-utils/src/main/java/com/sun/grizzly/tcp/
Compilation wise (thanks to Maven), doing {A} should not break any
current applications. But {B} will for sure breaks some of them.
How do we want to handle {B}? Should we:
[ ] Deprecate classes in http/src/main/java/com/sun/grizzly/standalone/
[ ] Move them and makes an announcement
I would think we should deprecated them but that might cause confusion.
What people thinks? I never handled such scenario before, so just to
make sure :-)
-- Jeanfrancois