Filip Hanik - Dev Lists wrote:
Right now I'm not hot about reading the data first in the container:
if done, it should be in InputBuffer,
yes, that is how I suggested it to be done. The AprBuffer was reading
the socket data in my checkin.
but could mean automagically discarding data, which could become a
very sneaky problem if the user doesn't code the right way but is
interested in the data.
yes, I prefer delivering the data. option 1
The point of your patch was not to preread the data as you are now
claiming, but instead about accepting entity bodies from invalid
requests. As I said, I prefer the current mechanism.
There are still some serious problems though, starting with the
current C2B and B2C converters which use far too much memory. I would
like to use the NIO converters instead, but they want to use
ByteBuffer and CharBuffer.
yes, and ByteBuffer and CharBuffer have historically been slower than
byte[] and char[], not sure if that is still the case.
I was talking about character encoding and decoding, which right now
sucks and is using tons of memory.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
