The point is that, with blocking I/O, you can scale better than most people expect. So for many projects NIO is overkill. There will still be a point at which it makes sense to choose NIO, and sacrifice some throughput for increased scalability, but most projects won't reach that point.
Comments
se7en replied ago:
Not quite new. Can you force close ( with immediate effect ) a stalled opened socket using the blocking api? Don't think so...
,
mheath replied ago:
This is old and stupid. Non-blocking NIO isn't about performance; it's about scalability.
Dan Dyer replied ago:
The point is that, with blocking I/O, you can scale better than most people expect. So for many projects NIO is overkill. There will still be a point at which it makes sense to choose NIO, and sacrifice some throughput for increased scalability, but most projects won't reach that point.
Voters For This Link (12)
Voters Against This Link (3)