mixing xml, dom and tdom
- From: "jkj" <kevin@xxxxxxxxxx>
- Date: 28 Nov 2006 13:19:59 -0800
Hello,
An "old dog" learning "new tricks" - like Tcl/Tk. I have inherited
some code which relies on tDOM but wish - no pun intended - to use SOAP
in the final S/W product. I am working primarily on [Fedora] Linux
systems.
First, when I download SOAP the documentation file
"tclsoap1.6.7/DESCRIPTION.txt" says:
Require: xml
Require: dom
Suggest: tdom
Second, in a modified version of the inherited code, the order of these
three "package require" statements
determines whether a segfault occurs or not (the XML package is not
used in the inherited code but would be required by the SOAP package):
package require tdom 0.8
package require tile
package require xml
....so that if "require xml" comes before "require tdom" a segfault
occurs [...how to trace segfaults in Tcl is another ??]. This seems to
tell me that including both of those packages is probably not a good
idea.
....should the inherited code not rely on tDOM since the inclusion of
package XML can lead to segfaults? but why is tDOM suggested for SOAP
if XML and DOM are required? From what I gather, tDOM is composed of
C-binaries for optimized performance, but it must leave out some
XML/DOM functionality? if so, how to avoid conflicts [segfaults,
apparently] where functionality has been duplicated?
What is the best approach to this brave new world: ditch tDOM or use
the entire stew? How do I best avoid hair pulling down the road? My
initial hunch is to develop without using tDOM and then include it in
stable products as a means of enhancing overall performance... but
maybe I am "missing the boat" on something...
Thanks,
-Kevin
.
- Follow-Ups:
- Re: mixing xml, dom and tdom
- From: Gerald W. Lester
- Re: mixing xml, dom and tdom
- Prev by Date: Re: backtracking and tcl...
- Next by Date: Re: ANNOUNCE: TkTreeCtrl 2.2
- Previous by thread: using TCL with sqlite database...
- Next by thread: Re: mixing xml, dom and tdom
- Index(es):
Relevant Pages
|
