Bypassing native storage operations by communicating protected data within locking messages using a lock manager independent of the storage mechanism

A method performed by a lock manager controlling access to protected data maintained in native storage independent of the lock manager, wherein the lock manager does not access said protected data from said native storage, the method comprising:

• receiving a release of a lock for use in controlling access to said protected data, the release including said protected data;
• identifying a next requester to be granted the lock in response to said receiving the release of the lock;
• copying said protected data from the release into a grant message;
• and
• sending the grant message to the next requester, the grant message including said protected data.

A tangible computer-readable medium storing thereon computer-executable instructions for performing steps by a lock manager for controlling access to protected data maintained in native storage independent of the lock manager, wherein the lock manager does not access said protected data from said native storage, said steps comprising:

• receiving a release of a lock for use in controlling access to said protected data, the release including said protected data;
• identifying a next requester to be granted the lock in response to said receiving the release of the lock;
• copying said protected data from the release into a grant message;
• and
• sending the grant message to the next requester, the grant message including said protected data.

A tangible computer-readable medium storing thereon computer-executable instructions for performing steps by a lock manager for controlling access to protected data maintained in native storage independent of the lock manager, wherein the lock manager does not access said protected data from said native storage, said steps comprising:

• receiving locking requests for a lock controlling access to said protected data from a first requester and a second requester;
• sending a first grant message to the first requester, the first grant message not including said protected data, and in response to identifying one or more requesters is waiting for the lock after the first requester, including an indication to return said protected data in the first grant message;
• receiving a first release message corresponding to the first grant message for the lock from the first requester, the first release message including said protected data;
• and sending a second grant message to the second requester, the second grant message including said protected data received in the first release message.

A lock manager controlling access to protected data maintained in native storage independent of the lock manager, wherein the lock manager does not access said protected data from said native storage, the lock manager comprising:

• means for receiving locking requests for a lock controlling access to said protected data from a first requester and a second requester;
• means for sending a first grant message to the first requester, the first grant message not including said protected data, and in response to identifying one or more requesters is waiting for the lock after the first requester, including an indication to return said protected data in the first grant message;
• means for receiving a first release message for the lock from the first requester, the first release message including said protected data;
• and means for sending a second grant message to the second requester, the second grant message including said protected data received in the first release message.