Hi all,
First thanks for the suggestions, after reading what has been posted
and giving it more thought this is how I think I am going to handle
page locking.
1) when a user enters the page to edit it, I will create a lock in a
lock table in my database. This way of someone else whats to edit
Hi all, I'm hunting for advice. I am looking for a way to lock a webpage
so that only only one person at a time can edit database data. Here is the
scenario, I have a database with a limited number of users who have write
access to the database, what I'd like to do is lock the editing page so
On 2007-09-06 Jose Galvez wrote:
I am looking for a way to lock a webpage so that only only
one person at a time can edit database data. Here is the
scenario, I have a database with a limited number of users who
have write access to the database, what I'd like to do is lock
the editing
Hi Jose!
I am going to face the same problem with the application I am coding,
it is a sort of CMS. I have thought about adding a boolean field
called lock just as you have used in the past. When a user requests
a page to edit and the lock field is not set to true, she can edit the
page
This is the plugin I intend to use, it can effectively block user
input if needed with notification:
http://www.malsup.com/jquery/block/#page
On Sep 6, 10:39 pm, voltron [EMAIL PROTECTED] wrote:
Hi Jose!
I am going to face the same problem with the application I am coding,
it is a sort of
Don't do this.
There is no way to make 100% certain that you don't end up with stale
locks. Sure, you can have an ajaxy thing that pings the server every
minute or so to say, I'm still editing this, but then the user goes
off to lunch and everyone is stuck until they get home. Or a malicious
Hmm..then things would be harder than I expected,maybe just warning
the user as David suggested would be enough, when the users ignore the
warning, tough luck. I wonder how the other CMS apps take care of this
problem.
On Sep 7, 1:29 am, Jose Galvez [EMAIL PROTECTED] wrote:
Hey voltron,
I'll
Hey voltron,
I'll take a look at the library, it looks pretty cool. David Turner,
makes some really good points and is really the main thing that I''ve
worried about. My current site (the one that needs lots of work read I
don't like the way I did it) uses a database to keep the locks, which I
On Thu, 2007-09-06 at 17:07 -0400, David Turner wrote:
Don't do this.
There is no way to make 100% certain that you don't end up with stale
locks. Sure, you can have an ajaxy thing that pings the server every
minute or so to say, I'm still editing this, but then the user goes
off to lunch
