Aleksander Slominski wrote: > another great feature would be ability to "lock" parser > buffer content so when i receive multiple character() call-backs > i know that XMLString offset and length will be valid > as parser will just create bigger buffer to keep larger content.
Sounds like you're asking for a more advanced buffer management system built into the parser. I was looking at implementing the "don't re-use character buffers" feature today and it's not as easy as I had hoped. So... I may end up implementing a system where the application can register a buffer manager and all of the components would ask the manager for new buffers, etc. Then, using this method, the Xerces2 parser would by default re-use buffers but a pull parser could install a new buffer manager that always created new buffers. But I need to do some more thinking on the topic... -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
