Seems like it was part of an e-mail I sent a couple of months ago.
Unfortunately I was placed on a different project soon afterwards and I
couldn't find the time to pursue this issue further.
(Although I am personally still interested:)

Wolfgang

> -----Original Message-----
> From: Gerald Richter [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 08, 2001 8:31 AM
> To:   Sablotron Mailing List
> Subject:      [Sab] Using "external" tree storage instead of the one
> provided by Sablotron
> 
> In the mailing list archives, I have found the following mail:
> 
> http://www.mail-archive.com/[email protected]/msg00276.html
> 
> >Sablotron uses a tree internally (as do all of the existing processors,
> >as far as I know). The access to the tree is not quite DOM-compliant.
> >But even if it were, you could hardly expect to be able to just pass on
> >the pointer to your in-memory tree to sablotron.
> >
> >What you could do is pass the tree to sablotron using SAX - walk through
> >the tree, triggering callbacks the way expat does. This makes the
> >serialization into flat text unnecessary.
> >
> >Now sablotron's able to construct a tree in this way; what's missing is
> >the interface that would let an outside user call the SAX callbacks. I
> >assume it wouldn't be hard to fill this in; if you'd like to try writing
> >this part (which may be quicker than waiting for us) we'll be happy to
> >give you more information. The file to look at is parser.cpp.
> 
> Has any progress made in this area ?
> 
> Another question: Is this tree internaly accessed via a C++ class ? If
> yes,
> would it be possible to override this class, so it doesn't return the
> content of the internal tree, but the content of an external tree that is,
> in my case, already build in memory by another application ? The same
> applies to the output: would be possible to provide a C++ that write the
> output back to the tree structure of the other application ?
> 
> Gerald
> 
> -------------------------------------------------------------
> Gerald Richter    ecos electronic communication services gmbh
> Internetconnect * Webserver/-design/-datenbanken * Consulting
> 
> Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
> E-Mail:     [EMAIL PROTECTED]         Voice:    +49 6133 925131
> WWW:        http://www.ecos.de      Fax:      +49 6133 925152
> -------------------------------------------------------------
> 

Reply via email to