CSharpCorner Just Published My Article : Multithreaded XML Documentfor Read/Write Access

  • Thread starter Thread starter Praxis Happenstance
  • Start date Start date
["Followup-To:" header set to comp.os.linux.advocacy.]
Check me out:

http://www.c-sharpcorner.com/Code/2004/July/MultithreadedXmlDoc.asp

Multithreaded XML Document for Read/Write Access
by John Bailo
Click to expand...

That's utterly retarded. Why not just bind the XmlDocument to a DataSet
if you want it to work like a database?

The XML classes are already thread-safe, and so is the DataSet.

Just create a XSD schema, then a master DataSet from it. Whenever a doc
comes in, do a DataSet.Merge() to bring in the new record.

Why would they publish that?!?
 
Hi Democritus Rising,

I think General Protection Fault is write about one thing,
C#'s routines for writing to ( unstructured ) XML fields
( e.g. DataSet.Merge() ? )
are Very probably threaded/mutexed already,

Hence, no need to check for collisions.
 
Jeff said:
Hi Democritus Rising,

I think General Protection Fault is write about one thing,
C#'s routines for writing to ( unstructured ) XML fields
( e.g. DataSet.Merge() ? )
are Very probably threaded/mutexed already,

Hence, no need to check for collisions.
Click to expand...

That is the stupidest conjecture I have ever heard.

--
incognito http://kentpsychedelic.blogspot.com/
fairgrounds http://home.earthlink.net/~jabailo/fairgounds/id6.html
storyteller http://home.earthlink.net/~jabailo/
latest article
http://www.c-sharpcorner.com/Code/2004/July/MultithreadedXmlDoc.asp
 
Jeff said:
Hi Democritus Rising,

I think General Protection Fault is write about one thing,
C#'s routines for writing to ( unstructured ) XML fields
( e.g. DataSet.Merge() ? )
are Very probably threaded/mutexed already,

Hence, no need to check for collisions.
Click to expand...

PS -- My next feat is to:

Apply the Mutex at the Node level ( field level locking )

--
incognito http://kentpsychedelic.blogspot.com/
fairgrounds http://home.earthlink.net/~jabailo/fairgounds/id6.html
storyteller http://home.earthlink.net/~jabailo/
latest article
http://www.c-sharpcorner.com/Code/2004/July/MultithreadedXmlDoc.asp
 
Hi Democritus Rising ( John B. ),

Re: My suggestion that C#'s routines for writing to XML fields
are probably threaded/mutexed already,
denecessitating collision checks.

You replied, <<
That is the stupidest conjecture I have ever heard. >>

John John John,

How could you ever know
if you fixed this ( imaginary ? ) collision problem
if you're not even sure whether it exists or not ! ?
 
["Followup-To:" header set to comp.os.linux.advocacy.]
Hi Democritus Rising,

I think General Protection Fault is write about one thing,
C#'s routines for writing to ( unstructured ) XML fields
( e.g. DataSet.Merge() ? )
are Very probably threaded/mutexed already,

Hence, no need to check for collisions.
Click to expand...

My MCSD in .NET says I'm definitely right.
 
General said:
A database needs a structure. You can't just keep adding crap with
different formats into a repository and call it a database.

And, an XML document does not meet the definition of a hierarchical
database. It's a hierarchy, but not an HDBMS.
Click to expand...

Here is someone thinking along the same lines ( though he is approaching it
from extending the idea of XML as a database, not so much the
threaded/multiuse aspect ).


Creating an In-Memory Database Using XML and XPath -- Part 1
http://www.15seconds.com/issue/010409.htm

Part II
http://www.15seconds.com/issue/010410.htm

Some interesting stats on performance in Part II:

1) SQL Query - New Connection per Query 58.953 ms

2) 8) Branched XML - Keywords + IDs as Tags - Grouped Keywords 2.340
 
Back
Top