Re: SmbTransport thread accumulation issues

BTW: I tried NIO once. Once. It is a crumby implementation of
select(2) from UNIX (which was always considered by many to be a
rather crude design in itself). NIO should be called "NoIO". I had
trouble just getting it to work reliably. And note that NIO would not
really help that much. It would only help in this particular case
where you want to communicate with 100 servers in parallel. Otherwise,
JCIFS is actually extremely efficient. The CIFS protocol allows for
multiplexing requests. Meaning you can send request A and B and get
the response for B before A. And JCIFS fully utilizes this. JCIFS can
touch every file on a workstation in under 10 seconds if the server
cache is hot. If the non-blocking implementation in Java were better I
might consider using it. But it's not.

Mike

-- 
Michael B Allen
Java Active Directory Integration
http://www.ioplex.com/


> On Tue, Oct 18, 2011 at 12:22 AM, Sebastian Sickelmann
...
>> problem is that jcifs is using blocking io instead of non-blocking io. I
>> made some experiments to use non-blocking io in jcifs and handle the io with
>> some small amount of threads, but it is far away from beeing ready for a
>> first review by the community and the commiters(i am not a commiter) of
>> jcifs.