Hey, Fernando!
What should I do when someone try lock an ID that already looked ??
Ah... that's where the locking mechanism comes in! This is what I have in my instructions.html file:
Any attempt to lock a resource that is already locked should cause the current thread to give up the CPU, consuming no CPU cycles until the desired resource becomes available.
So... the client trying to lock a record that is already locked should wait until that particular record is available. After getting its lock, then the update/delete should proceed normaly.
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD