2005/9/19, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
You're right. It doesn't release the bytebuffer allocated in its constructor. It will not be returned to the buffer pool but GC's by JVM. We have to find the better way to this. Any good ideas?
Trustin
-- I am surprised to see that the ByteBuffer used by CumulativeProtocolDecoder is
not explicitly released.
Given the ByteBuffer javadoc, I would assume that it should be.
You're right. It doesn't release the bytebuffer allocated in its constructor. It will not be returned to the buffer pool but GC's by JVM. We have to find the better way to this. Any good ideas?
Trustin
what we call human nature is actually human habit
--
http://gleamynode.net/
