Interrupted IO and AWT

Mon Mar 20 07:07:00 GMT 2000

Jon Beniston wrote:
> I seem to recall reading somewhere on Sun's Bug list that the interrupting
> of IO has in some form been deprecated. Does any one know whether this is
> the case? I ask, because I'm wondering whether I should implement this in
> the Win32 port. It seems as if there may be some overhead. Would this be
> worth it it the general case? Personally, I've never made use of it.

This was covered in the thread last week on Thread.interrupt():

http://sourceware.cygnus.com/ml/java-discuss/2000-q1/msg00418.html
I think the collective opinion on this list was that both interruptable
I/O and resource revocation are desirable in libgcj. If I had my
choice, interruptable I/O would be a configure-time option that could be
turned off for strict JDK compatibility (or better
performance/robustness in the case of Win32).
I remember reading somewhere that interruptible I/O can be implemented
on NT with async I/O, but that it won't work for 95/98 (which I couldn't
care less about, personally). That may have changed since I read it...
> Secondly, I'm quite interested in doing some work on implementing AWT (I'm
> more intrested in Client stuff myself). I was wondering if someone could
> clear up the position of this, esp. regarding the Classpath merger. I seem
> to recall that everything from Classpath is available except the AWT code.
> Now is this all AWT code or just the native implementation? IF I do use it
> what is the final result? That the executable is cover by the GPL? I can
> live with that for now...

>From looking at Warren Levy's latest patches, I'd guess that the libgcj
maintainers haven't given up on doing their own AWT port, independently
of classpath.
AWT would be great... you might consider a portable toolkit (GTK?)
though before it becomes too Win32-centric, so that other platforms can
benefit.
-- 
Jeff Sturm
jsturm@sigma6.com