SaxDriver for .NET parser
Brought to you by:
jeffrafter,
kwaclaw
Menu
▾
▴
Has anyone created a SaxDriver for the System.Xml .NET libraries? If so, please share, if not, it is in my interest to create one. Would this project be interested in the contribution to maintain with this distribution?
-Kevin
Well, I don't think such a thing exists.
Feel free to implement the SAX interfaces on top of System.Xml. It should pass the conformance tests we have included with the distribution so that we can include it as well.
Would you keep maintaining it?
What advantages do you think this would give you?
Karl
I would maintain anything I needed, which is pretty much everything. I'm porting a fairly thorough java library over to c#.
The only advantage I see is comfort that I'm using a parser that is fully featured and has performance of that or better than most. Since 'most' is the MS Xml parser, this seems to be an easy option.
If there were a Xerces equivalent (xerces-c?), I would be interested there as well if it had the kind of community that xerces-j has. I don't want to spend time defending or fussing about a parser, I just want it to work. Unfortunately the MS atmosphere here (checkout+lock, copy+paste, monolithic projects) already is dramatically different than the java culture (merge, reuse, open source). I would rather fight for those causes first as I see a greater reward.
As I'm going through, it seems like the SaxDriver.cs can be used to interface with System.Xml, am I incorrect?
Is there a JAXP equivalent in the c# world? NAXP? I hate to port code, and it seems that something like IKVM.net would work, but with the amount of issues listed above, biting off that much may be just too much for this culture to stand.
Any advice is welcome.
-Kevin
SAX for .NET includes a port of AElfred from Java.
It does perform DTD validation. We also include a wrapper for Expat, which is not a validating parser, but very fast, mature and conformant, as it is likely the most widely used Open Source parser. However, you need to deploy a native Dll.
If that is not enough, then by all means, go ahead.
Btw, the SAX for .NET interfaces are slightly different, wich is explained in the docs somewhere. The classes are even more different.
Also we are not built around the same classes as the original. All you need to do is implement the interfaces. SaxDriver is not part of the framework, but you can use that kind of approach, like it was done for AElfred.
I suggest you check out current CVS, as it has been converted to .NET 2.0.
Karl