The current code is using some 'interesting' tricks with the jk_pools -
it does some funny buffer allocations on the stack and use the buffer
to create a pool ( which itself is allocated on the stack ).
While this may have some performance benefits, the code is
extremely hard
to read, and
On Fri, 7 Dec 2001, GOMEZ Henri wrote:
The pool_open, etc will be removed - same for the buf[] based
allocation.
why not. Frankly you love too much java :)
I just like simple things.
Stack-allocating buffers and then creating ( stack-allocated ) jk_pools
in the buffer is not that simple,