Are you transcoding any data out of the SAX events? If so, are you deleting
the returned text?
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
----- Original Message -----
From: "Alexander Zeyliger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 16, 2001 1:38 PM
Subject: Progressive SAX parsing and memory
>
>
> Hello,
>
> I am using progressive sax parser to parse an incoming and potentially
> very long tcp stream (with my own input source class).
>
> In pseudo code this would look like this, of course:
> parser.parseFirst (input_source, token)
> while (! end of stream) {
> if (! parser.parseNext (token))
> break;
> }
>
> I assumed that the memory usage at each loop iteration should
> remain more or less constant, since in the SAX model all is done
> in callbacks, but the memory footprint keeps growing until the loop
> is over and parser goes out of scope.
>
> Is my understanding wrong? Is there a way to force the parser
> to clean up?
>
> Thanks,
> AZ
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
