This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
// Locks a record so that it can only be updated or deleted by this client.
// Returned value is a cookie that must be used when the record is unlocked,
// updated, or deleted. If the specified record is already locked by a different
// client, the current thread gives up the CPU and consumes no CPU cycles until
// the record is unlocked.
public long lockRecord(long recNo)
What Sun is trying to mean about cookie here in this interface. Are they trying to mean like this :
"returned value is a cookie which is nothing but it's same as magic cookie value in database file ()" ?
we have to randomly generate cookie value for each lock and the same generated must be used while performing other tasks like unlock/delete/update?
If you know the purpose of the lock and unlock methods, you'll be able to answer the question yourself. If you have read the ScjdFaq (as I suggested) you would also have read that the magic cookie is just used to identify database files.