Screen level Locking Process in c#

Question

0.00/5 (No votes)

See more:

Dear All,
Is there any process of locking the screen c# web application? for example some one open the page for edit/updating, if at the same time some other person if open the same page it should be in read only mode and it will alert the use that some one updating the page....

Posted 24-Jun-13 21:02pm

Any_India

Add a Solution

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)

Stephen Hewison · Answer 1 · 2013-06-24T23:09:00

The simple answer is yes. But it's a bit more complicated than that.

You're talking about record locking for which there are two main types. Pessimistic and Optimistic

Pessimistic is used to forcible stop someone editing a record. This is the type of locking you're asking about.

Optimistic is used when the record is saved. If the record has been changed since the user loaded it it needs to managed.

When hosting a website in IIS often you will use a technique called web gardening to get better performance for your website.

This means IIS will create multiple processes all of which are ignorant of each other because they don't share the same application memory space.

You therefore can't set a flag indicating the form is locked in memory. You have to find out of process storage to achieve this.

The simplest option is to create a table for managing which forms are locked. Update the table when a user locks and again when unlocks.

Then check the database when a user requests and edit and use this data to manage the response.