Comments on: Implementing an XML Data Provider for Oxite, Part I http://blog.hexadecimal.se/2009/05/03/implementing-an-xml-data-provider-for-oxite-part-i/ Being creative in the digital age Tue, 22 Jun 2010 05:15:09 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Q http://blog.hexadecimal.se/2009/05/03/implementing-an-xml-data-provider-for-oxite-part-i/comment-page-1/#comment-3 Q Mon, 04 May 2009 07:05:38 +0000 http://www.hexadecimal.se/2009/05/03/ImplementingAnXMLDataProviderForOxitePartI.aspx#comment-3 Good idea! I'll definitely take your advice. Good idea!

I’ll definitely take your advice.

]]> By: Erik Porter http://blog.hexadecimal.se/2009/05/03/implementing-an-xml-data-provider-for-oxite-part-i/comment-page-1/#comment-2 Erik Porter Mon, 04 May 2009 06:43:14 +0000 http://www.hexadecimal.se/2009/05/03/ImplementingAnXMLDataProviderForOxitePartI.aspx#comment-2 Neato. Keep up the good work. :) One suggestion might be to store some data twice. For example, maybe store each post (all the details about it except for sub objects like comments) as individual files, but then also store different lists of posts in another file like PostsByArea.xml, PostsByTag.xml, etc. It means you have to do a bit more work when saving, but reads will be really fast. This is sort of how Azure storage works. Neato. Keep up the good work. :)

One suggestion might be to store some data twice. For example, maybe store each post (all the details about it except for sub objects like comments) as individual files, but then also store different lists of posts in another file like PostsByArea.xml, PostsByTag.xml, etc. It means you have to do a bit more work when saving, but reads will be really fast. This is sort of how Azure storage works.

]]>