quote:Original post by Digitalfiend
You do realise that the Registry is just a binary file right? It doesn''t have any magical ability to enforce the rules you are talking about. The Registry API, the functions you use to access/manipulate the Registry, does. So basically:
Registry File is accessed using the Registry API
XML File is accessed using a XML Parser/API
I don''t see a lot of differences here - with regards to ensuring integrity. Both APIs enforce structure (layout and data type) and integrity.
Your argument is flawed in my opinion.
I think things are getting mixed up here :
Ok, the reg. if accessed via the API or reg edit tools inforce the data type being written to the reg. to the correct type.
XML files, again if accessed via teh API or a tool which enforces the type of data which is written.
HOWEVER the flaw with teh XML file is you CAN edit it with something like notepad which DOESNT inforce type checking. Now, I''m aware that the reg. could be edited with a HEX edit program however that does assume the user has (a) a hex editor and (b) can find the reg. files, where as am XML data file isnt overly hard to find
And just to add to the arguement, forget INI files, I''d go with a mix of the reg. for data which SHOULD be lost when windows is reinstalled and either custom data file or maybe a gzip compressed XML file (compressed to stop the user fiddling with it without the correct tools). As for location, there is a reason you have a my documents folder
Finaly, on the subject of ''huge reg. causing a slow boot'' my reg. size is currently 29meg, and Win2K restricts the size (54meg is its max), now, imho, thats not really a huge size and @ DMA66 loading speed it wont take very long to load that info memory.