Dare Obasanjo looks at the available options for representing XML-based data that is shared between components within a single process/AppDomain and discusses the design tradeoffs of each approach.
Best Practices for Representing XML in the .NET Framework
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Are there any special XML handling facilities in .NET for non-strict languages (e.g. Haskell) which don’t require those ugly hacks strict languages need to handle XML without having the whole document in memory.
[ I remember I wrote a comment like this to this article a couple of hours ago; it was a bit longer than this comment, but it seems to have vanished. Did I forget to hit the submit button? ]
No, you just posted it in the wrong thread:
http://www.osnews.com/comment.php?news_id=6477