Jeanfrancois Arcand wrote:
>>
>> The bug with the query string is because the URI constructor used URI
>> encodes URI component values, thus percent encoding was happening twice.
>>
>> I looked at the JavaDoc for:
>>
>> com.sun.grizzly.tcp.Request
>>
>> but there is no description for the URI information returned by these
>> methods:
>
> Yes. We gonna release Grizzly 1.7.0 this week and the next release will
> be an only 'improve documentation release'
>
Great!
>> Some questions/comments:
>>
>> - do you have or intend to provide a core Grizzly jar rather than
>> four separate jars?
>>
>
> Official release can be downloaded as a zip file from here (1.7.0 will
> most probably be release tomorrow):
>
> http://download.java.net/maven/2/com/sun/grizzly/bundles/
>
> But based on your feedback, I will start doing a single jar file like I
> was doing for Grizzly 1.0.x. so no needs to download many jars.
>
OK. That will make it much easier for those wishing to use Grizzly with
Jersey.
>
>
>> - i am going to create a GrizzlyServer server factory so it is possible
>> to deploy resources and create and start a "default" SelectorThread in
>> just one line of code:
>>
>> SelectorThread thread =
>> GrizzlyServer.create("http://localhost:9997");
>>
>> - i notice that in the unit test you put a sleep statement after the
>> thread that calls the SelectorThread.startEndpoint is called. It would
>> be very useful to have a blocking method on SelectorThread that
>> started the endpoint in a new thread and waited until the endpoint
>> said it is ready. Another way is for the method to return a
>> Future<Boolean>.
>
> That's a good idea. I did put the sleep to make sure the server is
> started. Let me try to have that in 1.7.0.
>
OK.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109