-1

for same reason I discussed with respect to extending SocketManager. I spent 
six months moving away from a single Block that is both a socket factory and 
a connection manager.

Besides doesn't nio work with ServerSockets still? You just go something like

ServerSocketChannel channel = myServerSocket.getChannel();
//do stuff with channel

So we should not need to change interface for 1.4 anyways - or am I missing 
siomething?

On Wed, 14 Nov 2001 04:47, Berin Loritsch wrote:
> The way we have the Socket handling API for Cornerstone does not provide
> us the flexibility to upgrade to non-blocking IO when it is available.
> I propose making the change from this:
>
>      public void connect( String name,
>                           ServerSocket socket,
>                           ConnectionHandlerFactory handlerFactory )
>
>
> to this:
>
>      public void connect( String name,
>                           String host,
>                           int port,
>                           ConnectionHandlerFactory handlerFactory )
>
>
> The change is using a host/port pair instead of the ServerSocket/Socket for
> the APIs.  One of the benefits of Non blocking I/O is an optimization of
> multiple sockets being handled in one thread!
>
> This allows the interface to be consistent now and when JDK 1.4 is finally
> released.  It also allows us to take advantage of a JDK 1.4 environment
> when it is available--without rewriting our apps!

-- 
Cheers,

Pete

-------------------------------------------------------
To fight and conquer in all your battles is not supreme 
excellence; supreme excellence consists in breaking the 
enemy's resistance without fighting. - Sun Tzu, 300 B.C.
-------------------------------------------------------

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to