I like... no! I
LOVE the way xml handles data (c#) root, node, element, attribute it allows you to get right down to the information. Like for the blog I am writing. Each entry has its own xml file (in an offline folder). Every image attachment has a "<image>" node so I just create a xmlList var and for loop though it. I know I can accomplish the same think in a database but I don't like the idea of using a single large column and very few small ones. Now that I think about it... I don't use xml for any rapidly changing items.
The program I am writing (my first with a purpose
) stores log type data (time, action, ect.) as xml. That’s only because I want a bunch of options for the ways you can export the data. Does that sound reasonable?