OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: C++ or IDL definitions for SAX

[ Lists Home | Date Index | Thread Index ]
  • From: Tyler Baker <tyler@infinet.com>
  • To: david@megginson.com
  • Date: Tue, 13 Oct 1998 15:55:31 -0400

david@megginson.com wrote:

> RJA@dip.co.uk writes:
>  > I'm currently looking into SAX and was wondering if anybody had any
>  > C++ or IDL definitions for SAX I could have ?
> Various people have offered to work on them, but none has yet
> appeared.  It should be simple to build a fairly-good SAX driver on
> top of EXPAT.

I am not so sure a CORBA IDL definition of SAX would be so useful anyways unless
you developed some efficient method of multiplexing the SAX events that get sent
over the network.  As far as C++ goes, I don't think a lot of people are doing
too much work here because any popular C++ tools for Windows have pretty much no
chance anymore of making an impact because of a very well known large company
having the reputation of cloning anything and everything of any value written in
C++ (looks like Java and a few other lesser known languages are the last bastion
of hope for the software industry).  Check out CNN on CNN/Fortune at 10:00 PM EST
tonight to see what I am talking about.  Writing software for the Windows
platform I don't feel makes any sense any more for a long-term perspective as any
useful software you actually create will be cloned in bad faith by a certain
well-known company.  Politics aside, as far as C++ on UNIX goes, I am not aware
of any vendors doing anything CORBA related with respect to XML.  I have not
checked InPrise's pages or IONA's pages in a long time, but if there is any XML
related CORBA application for UNIX, these folks are a start.

>  > On a slightly different note, are there are better alternatives to
>  > SAX for a simple event based API ?

Not really.  Event based API's basicly have to just parse the content of the
document and present it in raw form to the application in the form of Strings,
and character data.  There is no reason to make a process this simple any more
complex than SAX in the first place.  Pretty much all event-based parsers present
content to the application in a native form that is very much like SAX anyways,
so there is no real reason technically why SAX is inferior from a performance


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS