Last post Jan 13, 2010 08:09 AM by rtpHarry
Jan 12, 2010 12:19 PM|laskowik|LINK
Application Architecture design patterns
Jan 12, 2010 01:25 PM|rtpHarry|LINK
I wouldn't use xml as the data storage solution because only one user can safely use the file at a time.
I wouldn't use access as a solution because its a stripped down / basic sql database and there isn't really a good reason to do this any more.
SQL Server 2008 Express is a free database that has most of the features of the full sql server - certainly enough for a project such as this.
The ftp concept is interesting and you might have to use it in a different way depending on what your concept is for this.
Are you wanting to have a central control panel that can deploy the site from scratch?
Or a web developer sets up each of the sites and which includes a system for fetching the page content from a central database?
Jan 13, 2010 06:32 AM|laskowik|LINK
Jan 13, 2010 08:09 AM|rtpHarry|LINK
<div>with the xml it was similar idea as these
guys use here</div> <div>http://www.discovercraigavon.com/section.aspx?title=Accommodation</div>
<div>and when you modify the URL</div> <div>http://www.discovercraigavon.com/section.aspx?title=Accommodationsometext</div>
<div>and got this</div> <div>http://www.discovercraigavon.com/XML/about.xml</div>
<div>Not sure what you mean by "only one user can safely use the file at a time"?</div>
Nice site. The thing I was getting at is that because it is a filesystem object you cannot have multiple users editing parts of it at the same time.
<div>Or a web developer sets up each of the sites and which includes a system for fetching the page content from a central database?</div> <div>No,
I wouldn't really want individual websites to fetch from central database
(e.g. if sever goes down all three are down) that's why I'm looking what way would be the best to store data for each
individual website (XML, MS Access-you said not the best way).</div>
Ok then if you want to ftp over the xml files, or get the site to retrieve them, and use them in a read only capacity then I guess this wont be too bad. You could implement caching to store the xml data in memory to speed up the whole thing. I thought you
meant that the sites main database could run off xml.