Hi,
glassfish_at_javadesktop.org wrote:
> Thanks Jeanfrancois!
>
> I managed to get past this block by using the grizzly jar from Jetty 6.1.3 distribution ;-) but I'd prefer using the upcoming 1.5.1 bundle so I'm looking forward to it. I have one more question!
>
yes the bundle you are using is Grizzly http-based server 1.0.x instead
of 1.5.x.
> SelectorThread.startEndpoint() is apparently a blocking call. Is there a wrapper around it that can be used to manage the lifecycle of an endpoint without explicitly writing code for it?
Most of the time you need to spawn a new thread like:
new Thread(){
public void run(){
selectorThread.startEndpoint();
}
}
as I didn't wanted for a threading model for starting the server.
> I'm looking at Grizzly as a light-weight replacement for Jetty with NIO and, just for reference, Jetty's "Server" class supported non-blocking start() and stop() calls.
>
ah ah :-) Then I might need to re-think my solution :-) For sure I can
add the feature in 1.5 branch, but for 1.0 I'm affraid it will break too
many existing application.
Thanks for the recommendation!
-- Jeanfrancois
> [Message sent by forum member 'tnhashmi' (tnhashmi)]
>
> http://forums.java.net/jive/thread.jspa?messageID=219248
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>