Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a client server based windows forms application that needs an administrator only screen. The administrator functionality needs to be implemented in such a way that at any given time only one administrator can access that screen. The windows forms client application talks to the server using .NET Remoting. And the server side is distributed on multiple machines.
This can be done most easily through using a DB table. Typically the DB is already fault tolerant and is a safe resource to use for a shared lock scenario. Just have a lock table that contains some info about the locked resource, who has it, when, etc.
You can also use one of the various ‘state servers’ on the market to store lock state. This is introducing a failure point though, unless you invest in one of the newer distributed state technologies.
However, you are really setting yourself up for further issues. You’ll need a screen to allow forcing an unlock, viewing who has the lock, etc. You’re best off looking at why this lock is really needed. Is it a technology or business requirement? You can more easily and cleanly implement a pessimistic data updating scenario which would improve user experience.