• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX:Contractors exam locking server and not database

 
Bill Robertson
Ranch Hand
Posts: 234
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am having trouble understanding the following
requirement. It seems to me a contradiction.
Does this mean basically the only locking is done
from the server side? But if so, then what really is the difference to if you locked from
the database side.
Any help is greatly appreciated.
"You may assume that at any moment, at most one program is accessing the database file; therefore your locking system only needs to be concerned with multiple concurrent clients of your server. 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. "
 
Jim Yingst
Wanderer
Sheriff
Posts: 18671
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Only one program (the server) directly accesses the DB file. Any client program would make a request to the server, who would then access the file and report results.
 
Mike Southgate
Ranch Hand
Posts: 183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It means you may have many clients connected simultaneously but only one server or local client connected to the database file at once.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic