OpenSesame: David vs. Goliath
Mon 11 Jun 2007, 08:51 PMTweet
by Ben Langhinrichs
Copyright © 2007 Genii Software Ltd.
What has been said:
599.1. Nathan T. Freeman (06/12/2007 07:02 AM)
Consolidate every document in last year's Partner Forum into one long ODT.
By the way, are you using a standard parsing library? A 3rd party tool? How are you doing it?
Oh, and you should compare how long context.xml takes to load into the NotesSAXParser as well.
599.2. Ben Langhinrichs (06/12/2007 07:25 AM)
Nathan - I am using a highly customized version of an open source parser which I adapted for my own use (very liberal open source license is part of the reason, highly efficient and understandable C code is the other). I am also using a customized (but not as heavily) versiuon of the zlib library.
I thought about the SAX parser, but it would be apples and oranges. Since OpenSesame uses a full tree structure, and needs to for the kind of processing I do, there isn't much point in comparing with a SAX parser. Part of my goal is seeing how the total memory impact works out for large documents, and that is only an issue with a DOM tree.
As for consolidating documents, I may well do that, but I think I will use the Designer Help, as it has many more links and images and tables, which the partner forum does not. Still, I like the general idea. - Ben
599.3. Ben Langhinrichs (06/12/2007 07:40 AM)
OK, just for curiosity's sake, I tried this with the SAX parser, and it took 7 seconds, but it also leaked memory massively, which neither the NotesDOMParser or OpenSesame did. Interesting.
I am doing this in Notes 6.5.3, by the way. I'll try again with the Beta 3, but was determined to do tests with a production version of Notes to be fair.