Hi Bo,
don't think it's doable, or may be I just don't understand your idea
completely.
The reason is that transport can not create connections until it's not
started.
WBR,
Alexey.
On Mar 15, 2010, at 22:58 , ming qin wrote:
> Hi Bo:
> "It would be nice if Grizzly starts the transport when at least
> one connection is created and stops when all the connections are
> closed."
>
> Do you mean that Grizzly offers a daemon process which controls
> Transport life cycle ( Open/Shut Down) through that daemon process
> monitors number of valid connections?
>
> or
> You just don't like Transport offers start() method to end-users
>
> Ming Qin
> Cell Phone 858-353-2839
>
> --- On Mon, 3/15/10, Bo Li <b.li_at_sun.com> wrote:
>
> From: Bo Li <b.li_at_sun.com>
> Subject: Transport start/stop automatically on demand?
> To: users_at_grizzly.dev.java.net
> Date: Monday, March 15, 2010, 12:13 PM
>
> Hi Alexey
>
> Is there a way for the TCPNIOTransport to start and stop
> automatically? In our SDK, we don't want to expose Grizzly to the
> end users. It would be nice if Grizzly starts the transport when at
> least one connection is created and stops when all the connections
> are closed. This avoid the end users from having to call some sort
> of start/stop method explicitly.
>
> Thanks
> Bo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>