tranquillo
Technical User
I'm at the start of a project and we're looking at different opions for solutions...
the project is to create a webbportal. at the start there's going to be somewhere around 400 members with their own profile where they'll be able to show 10-15 pictures of "products" for sale or for show.
the users should be able to update their own profiles etc.
there'll be a lot of other funktions as well, such as lotteries, a webmagazine, forums etc. but this is mainly for the profiles.
and there'll be some serious marketing so we want it to be able to handle a lot of visitors and a lot more members within a year or two.
I'm not allowed to say too much about the content and what's for sale etc.
but at the moment we're planing to use asp.net(C#) and a database(msSql or mySql). but we're thinking of maybe using XML instead and DOM for the updates etc. using the database to create/update xml files.
I've been told that using scripts with DOM to create/update XML documents each time the database is updated is a very effective way, but I haven't been told why.
the way I see it is that using XML would result in a faster site for the user and that it's less demanding for the database, but would create a whole lot of xml files.
does anyone know the + and - for both soutions?
or does anyone know a site where I can read about it myself?
what I want is to be able to weight the CGI/database against XML/DOM/database agains eachother.
Tanks...
the project is to create a webbportal. at the start there's going to be somewhere around 400 members with their own profile where they'll be able to show 10-15 pictures of "products" for sale or for show.
the users should be able to update their own profiles etc.
there'll be a lot of other funktions as well, such as lotteries, a webmagazine, forums etc. but this is mainly for the profiles.
and there'll be some serious marketing so we want it to be able to handle a lot of visitors and a lot more members within a year or two.
I'm not allowed to say too much about the content and what's for sale etc.
but at the moment we're planing to use asp.net(C#) and a database(msSql or mySql). but we're thinking of maybe using XML instead and DOM for the updates etc. using the database to create/update xml files.
I've been told that using scripts with DOM to create/update XML documents each time the database is updated is a very effective way, but I haven't been told why.
the way I see it is that using XML would result in a faster site for the user and that it's less demanding for the database, but would create a whole lot of xml files.
does anyone know the + and - for both soutions?
or does anyone know a site where I can read about it myself?
what I want is to be able to weight the CGI/database against XML/DOM/database agains eachother.
Tanks...