Aleksander Slominski wrote: > i have implemented something like this already by wrapping > real reader with special reader that is cumulating input when > asked for. that allows me to keep buffer offsets from > XMLString and uses content in cumulative reader buffer > even though Xerces may reuse its internal buffer > (see below how i implemented CumulativeReader - it > works but is inefficient as it adds extra layer of indirection > and another buffer potentially for all IO operations).
The inefficiency is precisely the reason why I wouldn't want to use this type of approach. Besides, this approach has a hard limit of Integer.MAX_VALUE. The approach I'm thinking of simply manages the creation of buffers, not what is done with them. So the various parts of the code would still be in control of their own buffers but would simply request new buffers from the buffer manager/factory/whatever. -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
