No, saxjs cant be using all that memory. xml2js is probably doing some buffering of its own that justifies that memory usage.
I've seen the saxjs code and the buffers are very well kept, plus you can set a limit after which buffers will be purged. Nuno On Fri, Mar 2, 2012 at 11:07 AM, Wan Li <wanli...@gmail.com> wrote: > On Fri, Mar 2, 2012 at 7:04 PM, fent <roly...@gmail.com> wrote: >> >> Have a look at https://github.com/isaacs/sax-js > > > xml2js is built on top of sax-js. I even hacked version to utilize the > streaming API provided by sax-js, but doesn't help too much. > > -- >>: ~ > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
