> I have to ask Tod - are you actually using AxKit and/or XML::LibXML? This
> stuff is done already. XML::LibXML *is* a C based DOM. AxKit *does* cache
> the DOMs.
>
> For Steve, the answer is that libgdome features intelligent garbage
> collection. At the moment for XML::LibXML we've had to hack on a form of
> garbage collection wrapped around Perl's GC features, but it's about as
> stable as a Callista Flockhart in a force 10 gale. Ultimately the
> intention is to re-write XML::LibXML to work around this, but that's going
> to take time, and almost not worth it when XML::GDOME has done it already.

Matt, I understand that LibXML is a wrapper around a C processor, but what I 
was saying is that GDOME implements DIRECT Perl level access to the DOM tree 
produced. Last time I checked LibXML had about 4 methods, which amounted to 
you could pass the DOM to LibXSLT or a few other variations with filehandles 
etc. 

I guess what I'm saying is, suppose you wanted to implement something like 
SOAP::Lite on top of libxml. It just doesn't give you the ability to do much 
with the parsed DOM tree, and SOAP::Lite needs fine grained access to the 
resulting data structures. 

Maybe my understanding of LibXML is out of date, but the pod for the version 
I have says basically "DOM level access is something for the future". I have 
way too much stuff to do to keep up with all of Matt's advances, hehe. 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to