xml
Occasionally I'll write about things that I find sort of mildly, vaguely thought provoking, and somehow that writing turns out to be ragingly controversial once posted here. Case in point, XML: The Angle Bracket Tax. I'm still encountering people online who almost literally hate my guts
xml
Everywhere I look, programmers and programming tools seem to have standardized on XML. Configuration files, build scripts, local data storage, code comments, project files, you name it -- if it's stored in a text file and needs to be retrieved and parsed, it's probably XML. I
xml
Here's a helpful article that documents some common pitfalls to avoid when composing XML documents. Nobody wants to be called an XML Bozo by Tim Bray, the co-editor of the XML specification, right? There seem to be developers who think that well-formedness is awfully hard -- if not
xml
Let's say you wanted to generate and render this XML fragment: <status code="1" /> <data> <usergroup id="usr" /> </data> Here's a fully object-oriented way of building it: System.Text.StringBuilder sb = new System.Text.
xml
I have no problem with XML. It's a fine way to store hierarchical data in a relatively simple, mostly human-readable format. But I've always disliked its companion technology, XSLT [http://www.w3.org/TR/xslt]. While useful in theory-- "using a simple XSLT transform, XML
network sniffer
I’ve occasionally used network sniffers in the past, but with the rise of REST, XML, SOAP and .NET Remoting in the last year, sniffing has become an essential part of my development toolkit. I’ve evaluated a bunch of network sniffers, including the excellent open-source Ethereal, but the one