This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: java.net: Classpath vs. libgcj Comparison
Bryce McKinlay wrote:
> > It might
> > make sense to rename the latter to UnixSocketImpl or something, but I
> > see no reason why the existing class can't continue to use
> > FileDescriptor (except perhaps the timeout issue someone mentioned).
> > We should probably also create and installed an explicit
> > UnixSocketImplFactory rather than having that be implicit.
>
> I agree. The problem of implementing socket timeouts could be solved at the
> InputStream/OutputStream level. Rather than having {Plain|Unix}SocketImpl
> create a FileOutputStream, we could have a native SocketOutputStream that
> wraps the filedescriptor calls with select() if required. Unfortunatly this
> means we'll need a natPosixSocketOutputStream, natWin32SocketOutputStream,
> etc...
Not necessarily. If Socket{Input|Output}Stream classes simply call back
to the underlying SocketImpl object they need not have any native code.
--
Jeff Sturm
jeff.sturm@appnet.com