[Saxdotnet-devel] SAX holes
Brought to you by:
jeffrafter,
kwaclaw
From: Elliotte H. <el...@me...> - 2004-12-07 20:29:30
|
I know of two holes in the SAX API where it fails to address all possible XML documents. It would be worth considering these and if possible plugging them: 1. Maximum limits: XML places no size limits on anything. SAX does. There cannot be more than 2.1 billion or so attributes in an element, characters in an attribute values, characters in an element name, data in a processing instruction. Possibly .NET does not have these issues. Does .Net have a maximum string size or array size like Java does? If it does, this concern should at least be addressed in the documentation if not solved. 2. Skipped entities in attribute values: SAX says nothing about how to handle these. Most parsers just drop them out, though a few add something like &entity; to the attributer's string value. This should be fixed, but it might require some major redesign. -- Elliotte Rusty Harold el...@me... XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim |