How to lock application object in C# web

Question

0.00/5 (No votes)

See more:

I have created web application in which an application no created and saved in database .When entry opertator users looks dashboard he tries to access application but if any other user is using that application then it creates problem.How to avoid proper way for multiple user should not use same object.

What I have tried:

We tried to set lock using database but in database it create problems in unlocking
Also I used locking methods but in this case how to lock this application object so that no other user should use it .
.So please help me to get proper solution.
thanks in advance ....

Posted 7-Oct-16 3:02am

sp_suresh

Updated 7-Oct-16 5:00am

Add a Solution

Comments

[no name] 7-Oct-16 9:06am

Being the we don't know anything at all about your project or your problem, re-architect your project in such a way that sharing objects does not cause a problem.

F-ES Sitecore 7-Oct-16 10:47am

The problem you have is that the web is stateless so your site doesn't know who is editing what, or looking at what. If a person begins to edit something then goes away to lunch, or simply doesn't save or complete the edit then that item remains locked forever.

Instead of locking items the best solution is to have a timestamp for your records. So if you are editing "Person A" then that person's record in the db will have a timestamp column that your site will read and store. When the record is saved you check the timestamp is the same as it was before, save the data and update the timestamp. If you find the timestamp isn't the same then that means someone else has edited the data in the meantime so you can tell this to the user when they try and save and give them appropriate options to resolve the conflict, such as abandon their changes or override the previous person's changes, or somehow merge the two.

sp_suresh 10-Oct-16 2:13am

F-ES Sitecore ....Thank you very much & sorry for delay .As you suggested we already maintained changed log.So we can track also changes done by user. Also We will check your solution.....

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Midi_Mick · Answer 1 · 2016-10-07T03:40:00

Solution 1

I think what you are looking for here is a named mutex - these work like locks, but across process boundaries. There is a little bit of work involved in learning to set them up properly, but if you look at the MSDN documentation, I'm sure you'll get there. A good starting point would be here[^].

Posted 7-Oct-16 3:40am

Midi_Mick

Comments

sp_suresh 10-Oct-16 2:24am

thanks and sorry for delay.We are studying mutex...

#realJSOP · Answer 2 · 2016-10-07T05:00:00

Your problem is probably because the record is locked in the DB, but for whatever reason, it may not be unlocked. You also haven't sufficiently engineered your locking strategy.

First, maintain some sort of indication in the DB when a record was locked and by whom. Then you can:

0) When the browser session ends, have it unlock any records that are locked by the user.

1) Establish some sort of timeout that will allow you to automatically unlock a given record.

2) Include code in your stored proc that will not allow a record to be updated by a user unless that user currently has it locked.

Nobody here can provide anything more than advice. How you engineer your locking/unlocking solution is wholly dependent on a) the database, and b) the nature of the web site.