Locking and Handling Concurrency

Question

0.00/5 (No votes)

See more:

Dear Team,

I am developing a web application and the problem is how to handle Locking....

For ex.I have a TransactionId=1234 and it is opened by some other user so it should prompt a message to another user if he/she try to open the same transaction Id(1234) that TransactionId(1234) is locked by user(username) on this(MachineName) machine.

Thanks
Sukhen Dass

Posted 21-Oct-11 20:20pm

sukhen dass

Add a Solution

Comments

Xeshan Ahmed 22-Oct-11 4:34am

you have to store global lock state and on every transaction check the state of lock and make appropriate decision

1 solution

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)

Sander Rossel · Answer 1 · 2011-10-21T23:38:00

What you describe is Pessimistic Concurrency. This is no easy task and I don't think anyone will be able to easily answer that. However there are some links you could check. What is Pessimistic Concurrency[^], Introduction to Concurrency Control[^], Optimistic and Pessimistic Concurrency - A Simple Explanation[^].
As you can read there are some implications with pessimistic concurrency, deadlock possibly being the most dangerous. There are probably various way to handle this. Some ORM's might be able to handle this for you, such as Teleriks OpenAccess ORM[^]. You could also use, for example, a service that keeps track of who locks what entity. But once again, there really is no easy way to do this.

I hope this is at least somewhat helpful, even though it does not really answer your question :)