This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
for lock/unlock part in the specs its mentioned " the unlock method simply removes the lock from the specified record, if an attempt is made to unlock a record that has not been locked by this connection, then no action is be taken. " this action could'nt occur and shouldnt be by the spec. why ? becuse its mentioned in the spec. " the lock method block until a requested lock can be applied" , and so it cannot be unlocked unitl its locked before, and trivially unlock comes after lock, so its for sure only the record that lock is the one that can unlock, since if others are to lock what is locked they have to wait. I think the complexity of monitoring what connection for a lock is not neccessary. although its mentioned in the specs. I think this part is trivial and wont add something to the locking programming. and so connection class/object is not necessary, and the lock/unlock methods signature mentioned in the specs are enough. any comment ??
If you want to get the best help and advice on Java anywhere, you need to change your display name to a first and last name. Read thru this thread to see some opinions on this matter: Unlock ignoring bogus requests
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
Joined: Sep 22, 2002
Thanks a lot, I believe this reference is useful. Thanks.