> The recv-q appears to be non-empty, and yet the loop *must* be saying
> c.in.available()==0, so why can't we read that last byte and close the
> socket? Or how can we better know when the connection is lost and clean
> up?
I posted about this just a few days ago. available() won't return an error
on a closed Socket's InputStream. Javadoc actually says:
The available method for class InputStream always returns 0.
But this obviously isn't true... oh well.
-cm
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev