You're probably right. Use JSON.Net. Easy Peasy


>Have not benchmarked it in Dotnet, but my guess is that reading / parsing JSON is also faster than processing XML.
>
>When comparing such stuff a few years ago, one of the fastest ways to build an internal tree structure with different node "properties" was to runtime compile dict-heavy python source code, probably because the rules are tighter, similar to Execscript or [compiling and running] an unincluded prg in a foxpro app. As JSON is similar to JS source and even part of ECMA, the assumption seems reasonable, esp. if targeting different browsers.
>
>Precompilation (even back into JS source for web apps) of parts is another option - see Mithril docs for speed of specialized JS code vs. typical HTML ;-))