>
> Looks good. Are you familiar with the ACE project? Judging
> from patterns and
> naming I would say yes? If not you should check it out ;)
>
I had a short look at it. All the work I done before was from scratch,
implementing ides from different papers like SEDA, Actor - Reactor
patterns.
> > interface AsynchronousConnectionManager
> > {
> > // more avalon like way of retriving connector
> instances? this is
> > simple because connector is a nested class
> > public void createConnector();
Bad typo.. public Connector createConnector(); makes more sense ;)
> > public void addConnector(Connector connector);
>
> I don't understand the need for this method?
I think you're asking why using Connector and Acceptor classes instead
of moving their methods directly to the manager, aren't you? This is
done to prevent to select which service handles a connection after it is
established. This way you create a connector and/or acceptor in your
service, and you get only the events you are interested in.
>
> > public void start();
> > public void stop();
> > public boolean isRunning();
> > public boolean isStopping();
> > // will disappear in avalon impl... compose/dispose instead?
>
> Yep - all the above will be handled by the container and
> doesn't need to be
> in the service interface.
>
> --
> Cheers,
>
> Pete
>
> --------------------------------------------------------------
> "Science is like sex: sometimes something useful comes out,
> but that is not the reason we are doing it" -- Richard Feynman
> --------------------------------------------------------------
>
Great quote ;)
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
