[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] Error and Fatal Error
- From: Stephen D Green <stephengreenubl@gmail.com>
- To: David Carlisle <davidc@nag.co.uk>
- Date: Sun, 17 Jul 2011 21:56:47 +0100
Cross-posting, but yes it would be possible to do that
but mean handling all the weird and wonderful angle
bracket stuff ourselves in code (and without MicroXML
simplification so we could have XML with namespace
declarations apearing just about anywehere, any legal
whitespace anywhere, etc, etc). Why write our own
XML parser when there is a proper one in the .NET
framework all tested and standards-conformant. All
we need to do is simply check the content of each
element for illegal characters. Do we really have to
write an XML parser just for that?! The idea of .NET
is to use a framework based on RAD and not have
to write things from scratch (unlike, in my experience,
Java which seems to take developers ages to write
a typical webform). The only sticking point seems to be
these clauses in the XML spec making the .NET parser
a little too quirky and fussy. I think that's a fair assessment
from what I'm hearing on this list.
----
Stephen D Green
On 17 July 2011 21:42, David Carlisle
<davidc@nag.co.uk> wrote:
On 17/07/2011 20:30, Stephen D Green wrote:
because the XML content includes data input into textbox controls, etc
in a webpage and we do not want to prevent users inputing '<' and '&'
but surly it's fairly trivial to do a string replace on all such input
to change < and & to < and & a lot simpler (and more reliable) than suggesting the entire xml parsing model changes.
David
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]