 | | | Freeware ActiveX XML parsers | Freeware ActiveX XML parsers 2005-05-03 - By Brad Friedman
Back
Unfortunately I have not worked with any XML in a activex environment yet.
If we were talking Java, I'd point you to the apache foundation and
their Xerces project.
http://xml.apache.org/
Infact I'm looking at the documentation for Xerces now (I've not used it
in a couple of years at least) and am seeing that they have COM
bindings... so maybe it is useful to you.
In a dotNet environment I'd point you to microsoft's own internal XML
parsers which are part of the dotNet runtime.
And as stated: I'm not familiar enough with Python to navigate their XML
offerings and make a suggestion.
I've never looked at the msxml sdk before you mentioned it. However it
does seem to have a SAX styled parser (called SAX2)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/html
/xmmscXML.asp
Their DOM may be slow as you indicated but I can't imagine their SAX
parser would be particularly slow. The bottlenecks in such parsers are
usually associated with getting the stream itself. Or... possibly the
overhead associated with COM calls. In which case using a pure Python
solution might help... or going pure C++ might help.
Of course any of these solutions have the added complication of XSI
Linux compatibility to deal with as well.
home some of that helps.
-brad
Bradley R. Gabe wrote:
> Thanks, Brad! Good stuff for an XML newbie like myself.
> I'm actually a rigger, not a programmer. I just find myself writing a
> lot of code for some reason.
>
> Large file sizes are indeed likely, as we are dealing with a lot of
> name space and float point values to store in a text format. The
> Chilkat parser has built in compression and streaming, though I have
> no clue if that would result in faster file reads.
>
> If a SAX type parser is better for 3D-sized data sets, got any rec's
> for a parser in mind?
>
> -Brad
>
>> no one is more surprised than I that I have a recommendation... or at
>> least some useful information (I was sure I was gonna be a rigger...
>> not a programmer... wrong again).
>>
>> I took a quick look at the Chilkat XML docs to make sure. And I
>> think that particular parser is a DOM style parser. Which has
>> repercussions.
>>
>> Stepping back a second.
>>
>> According to w3c there are two basic types of XML parsers (well, two
>> that they foresaw and wrote about). DOM type and SAX type.
>>
>> DOM (Document Object Model) type parsers will parse the entire XML
>> file and load it into memory to be manipulated like a node tree.
>>
>> SAX (Simple API for XML) type parsers are event driven. As an XML
>> stream is read, it fires off callbacks to your code to do with the
>> data what you will.
>>
>> (note: in most cases a DOM style parser is written on top of a SAX
>> style parser. It uses the SAX parser to build the DOM tree and then
>> hands it over to you.)
>>
>> Without a doubt, DOM parsed XML docs are a lot more fun and intuitive
>> to work with. However, since the entire document ends up loaded into
>> memory in most cases, its not always reasonable to use a DOM style
>> parser on large data sets. And since we are talking about 3d here...
>> large data sets are a possibility (dare I say likely?).
>>
>> So, if you're looking for a good solid XML base to work off of for
>> working in XSI, I'd look to something that has both types of parsers
>> to work with. Though I'm kinda new to the ActiveX world... so I
>> don't have any specific recommendations as to what might satisfy said
>> suggestion.
>> Though I'd be willing to bet Python has a number of good XML parsers
>> available.
>>
>> -brad
>>
>> Bradley R. Gabe wrote:
>>
>>> Howdy List-
>>>
>>> I'm experimenting with some XML based toolsets in XSI and have been
>>> using the free Chilkat Xml parser which I'm finding to be faster
>>> than MSXML.
>>>
>>> Anybody out there have recommendations for other XML engines and
>>> editors, as well as file browsers, etc? This is all fun and new to
>>> me and may force me to use Python to take better advantage of its
>>> XML features. :-)
>>>
>>> Thanks
>>> -Brad
>>>
>>> ---
>>> Unsubscribe? Mail Majordomo@(protected) with the following text in
>>> body:
>>> unsubscribe xsi
>>
>>
>>
>> ---
>> Unsubscribe? Mail Majordomo@(protected) with the following text in
>> body:
>> unsubscribe xsi
>
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in
> body:
> unsubscribe xsi
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|