Forums Register Login

Use of Lock/Unlock with local client/db access!

+Pie Number of slices to send: Send
What is the use of Lock/Unlock when you are running both client and database locally - I mean there cannot be more than one client locally so do we need Lock/Unlock in that case.
+Pie Number of slices to send: Send
Don't sweat it, I say. I don't think it hurts anything to use the lock code when you're in local mode.
+Pie Number of slices to send: Send
I agree. I've seen posts from people who implemented their database locking logic based on the local/remote connection modes of their data clients.
The database should not care what connection mode the database client is operating in. So your database locking/unlocking logic shouldn't concern itself with such things.
Now if the data client code wants to call lock & unlock differently based on the connection mode, that's fine... but probably un-needed and creates more code to test, maintain, document and risk introducing bugs.
+Pie Number of slices to send: Send
Thanx guys, for the advise. It seems like I should do lock/unlock no matter whether I am using local client access or networked access - for simplicity sake!
I will open the floodgates of his own worst nightmare! All in a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 623 times.
Similar Threads
URLyBird 1.3.2: Where do you call the Data class's lock() and unlock() method?
lock & unlock in local mode
NX: Contractor locking
Passed with 150/155
Implementing Lock/Unlock using Event delegator
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 12:49:28.