Github user rschmitt commented on the issue:
https://github.com/apache/httpcomponents-core/pull/91
@ok2c Your other option is to make minimum buffering requirements an
explicit part of the contract, by doing one of the following:
1. Throwing an exception if an implementation of `initCapacity` returns an
insufficient initial size
2. Passing your buffering requirements to the implementation as part of the
`initCapacity` call and requiring the implementation to be able to buffer at
least that much data
I don't have direct experience with the selector API in NIO, so it's tough
for me to follow your description of the problem. Can't input event interest be
set again as part of the `CapacityChannel#update` implementation (called back
whenever data is read from the client's stream buffer)?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
