|
|
You're in the
c#
group:Web Services Shared Resource/Memory
c#:
How can I share resources across all users of a web service for read/write access. *Situation* *one*: I want to have an in memory counter that all users of the webservice could access. Call it g_count. Then I create a web method called Update_g_count. public int g_count( int incr ) { g_count += incr; return g_count; } So, how do I define g_count so it's global across all users? *Situation* *two*: I have an XML file that I want to load into an XmlDocument. I want to set up a Web Method that uses XPath to find a node, and then change the value of the InnerText. How do I put this XmlDocument into memory so all users can update it without collisions when they try to update the nodes? Do I need to use a mutex ? How can this mutex apply across all users of the web service ? Do I put it in global.asax ? -- incognito
Hi,
You can use the Application object to store the object accross web services. public int g_count() { ...... // Get the count int gcount = (int) Context.Application["gcount"]; ...// Process it //Save it back Context.Application["gcount"] = gcount ; } Although its not a recomended way to share such resources in read/write mode when specially in the case of web applications. You can using the lock C# keyword to lock access to the object while you are modifying it. -- Regards, Saurabh Nandu AksTech Solutions, reflecting your needs... [ www.AksTech.com ] [ www.MasterCSharp.com ] [quoted text, click to view] "Grandpa Pete" wrote:
> > How can I share resources across all users of a web service for read/write > access. > > *Situation* *one*: > > I want to have an in memory counter that all users of the webservice could > access. Call it g_count. > > Then I create a web method called Update_g_count. > > public int g_count( int incr ) > { > g_count += incr; > return g_count; > } > > So, how do I define g_count so it's global across all users? > > *Situation* *two*: > > I have an XML file that I want to load into an XmlDocument. > > I want to set up a Web Method that uses XPath to find a node, and then > change the value of the InnerText. > > How do I put this XmlDocument into memory so all users can update it without > collisions when they try to update the nodes? > > Do I need to use a mutex ? > > How can this mutex apply across all users of the web service ? > > Do I put it in global.asax ? > > > > -- > incognito > http://kentpsychedelic.blogspot.com/
You say that this is not a 'recommended' way to share resources in web applications. Can you suggest a recommended way? Specifically, I want to share access to an XmlDocument across all users of my web service. I want them to be able to query and update nodes on the document. [quoted text, click to view] Saurabh Nandu wrote: > Hi, > > You can use the Application object to store the object accross web > services. > > public int g_count() > { > ..... > // Get the count > int gcount = (int) Context.Application["gcount"]; > > ..// Process it > > //Save it back > Context.Application["gcount"] = gcount ; > > } > > > Although its not a recomended way to share such resources in read/write > mode when specially in the case of web applications. > > You can using the lock C# keyword to lock access to the object while you > are modifying it. > -- incognito @ http://kentpsychedelic.blogspot.com/ Man is the best computer we can put aboard a spacecraft ... and the only one
hi,
XML is best when its used as a data exchange document, and not as a database as such. The reason i don't recomend using it as a database (shared amongst users) is that you end up writing a lot of locking code to ensure that when one user is updating the document others cannot write to it and things like that. Now suppose 2 users tried to update at the same time, ones request will pass through other will fail since the document gets locked. FOr multiple read/write the best source to store data is a database!! Its meant to help you d multiple read/writes without locking the users. -- Regards, Saurabh Nandu AksTech Solutions, reflecting your needs... [ www.AksTech.com ] [ www.MasterCSharp.com ] [quoted text, click to view] "Donnie Darko" wrote:
> > You say that this is not a 'recommended' way to share resources in web > applications. > > Can you suggest a recommended way? > > Specifically, I want to share access to an XmlDocument across all users of > my web service. I want them to be able to query and update nodes on the > document. > > > Saurabh Nandu wrote: > > > Hi, > > > > You can use the Application object to store the object accross web > > services. > > > > public int g_count() > > { > > ..... > > // Get the count > > int gcount = (int) Context.Application["gcount"]; > > > > ..// Process it > > > > //Save it back > > Context.Application["gcount"] = gcount ; > > > > } > > > > > > Although its not a recomended way to share such resources in read/write > > mode when specially in the case of web applications. > > > > You can using the lock C# keyword to lock access to the object while you > > are modifying it. > > > > -- > incognito @ http://kentpsychedelic.blogspot.com/ > > Man is the best computer we can put aboard a spacecraft ... and the only one > that can be mass produced with unskilled labor. -- Werner von Braun
[quoted text, click to view]
Saurabh Nandu wrote: Actually, I already created a Windows service that allows multithreaded access to an XmlDocument for simulaneous 'users' to read/write. I use the Mutex class. I mutex is like queueing system, it takes in requests from multiple threads or sources and let's them in one at a time, so there is no collision. Xml /is/ a 'data' base. What you are referring to as a database is a Sql relational database. Tables in a relational database are orthogonal. Each record has all the fields of all the others, and no more. Xml is a hierarchical database. But, it is also 'ragged'. Not all nodes have to have the same attributes, or child nodes. For many uses, Xml could be idea. That is why I am interested in creating this web service. I also feel that many web 'database' applications need only a single table with very complicated nodes. In that case, a relational database, such as sql server, is the *wrong* choice for web-data applications; and Xml could be *very* useful. [quoted text, click to view] > hi, > > XML is best when its used as a data exchange document, and not as a > database as such. The reason i don't recomend using it as a database > (shared amongst users) is that you end up writing a lot of locking code to > ensure that when one user is updating the document others cannot write to > it and things like that. > > Now suppose 2 users tried to update at the same time, ones request will > pass through other will fail since the document gets locked. > > FOr multiple read/write the best source to store data is a database!! Its > meant to help you d multiple read/writes without locking the users. > > > -- incognito @ http://kentpsychedelic.blogspot.com/
Hi,
If you read my post the main reason I have stated to not go for XML as a database, is that you need to write a lot of code to get multi-threading right! Not everyone is able to write multi-threaded applications correctly...plus you loose all the other features RDBMS system provide to you like Transactions, Security, etc. I agree with the benefits you have listed which would warrent using XML as a datasource, but for most users they tend to use it in the same format as one uses a RDBMS. -- Regards, Saurabh Nandu AksTech Solutions, reflecting your needs... [ www.AksTech.com ] [ www.MasterCSharp.com ] [quoted text, click to view] "Guy LaRouche" wrote:
> Saurabh Nandu wrote: > > Actually, I already created a Windows service that allows multithreaded > access to an XmlDocument for simulaneous 'users' to read/write. I use the > Mutex class. I mutex is like queueing system, it takes in requests from > multiple threads or sources and let's them in one at a time, so there is no > collision. > > Xml /is/ a 'data' base. > > What you are referring to as a database is a Sql relational database. > Tables in a relational database are orthogonal. Each record has all the > fields of all the others, and no more. > > Xml is a hierarchical database. But, it is also 'ragged'. Not all nodes > have to have the same attributes, or child nodes. > > For many uses, Xml could be idea. That is why I am interested in creating > this web service. > > I also feel that many web 'database' applications need only a single table > with very complicated nodes. In that case, a relational database, such as > sql server, is the *wrong* choice for web-data applications; and Xml could > be *very* useful. > > > hi, > > > > XML is best when its used as a data exchange document, and not as a > > database as such. The reason i don't recomend using it as a database > > (shared amongst users) is that you end up writing a lot of locking code to > > ensure that when one user is updating the document others cannot write to > > it and things like that. > > > > Now suppose 2 users tried to update at the same time, ones request will > > pass through other will fail since the document gets locked. > > > > FOr multiple read/write the best source to store data is a database!! Its > > meant to help you d multiple read/writes without locking the users. > > > > > > > > -- > incognito @ http://kentpsychedelic.blogspot.com/ >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |