A
Artur Sorszegi
Hi!
There a lot of examples and talk about using an XML file as a datasource.
Given a DataSet object, you can easily load data from the XML file, and
display it in for example a DataGrid, or bind the data to other controls.
You could even edit the data, and save it back using the DataSet objects'
WriteXml method. But these resources fail to specify one thing, namely, if
this causes any problems when multiple users use the application at the same
time? I think you could use the expression concurrency problem for it, where
two users start using the data at the same time (for example), and both make
changes, first the first saves it, then the second. My feeling is, that this
could overwrite changes by one user with changes of the other.
Is this really so? Can it be prevented? In many cases, an XML file could
server just as well as a database, but having this problem, and not even
knowing if it works, make it not a so good solution.
I assume, that page requests can be processed in parallel by ASP.NET (or
else this would not be a problem).
Anyone, any ideas?
Thanks
There a lot of examples and talk about using an XML file as a datasource.
Given a DataSet object, you can easily load data from the XML file, and
display it in for example a DataGrid, or bind the data to other controls.
You could even edit the data, and save it back using the DataSet objects'
WriteXml method. But these resources fail to specify one thing, namely, if
this causes any problems when multiple users use the application at the same
time? I think you could use the expression concurrency problem for it, where
two users start using the data at the same time (for example), and both make
changes, first the first saves it, then the second. My feeling is, that this
could overwrite changes by one user with changes of the other.
Is this really so? Can it be prevented? In many cases, an XML file could
server just as well as a database, but having this problem, and not even
knowing if it works, make it not a so good solution.
I assume, that page requests can be processed in parallel by ASP.NET (or
else this would not be a problem).
Anyone, any ideas?
Thanks