• Post Reply Bookmark Topic Watch Topic
  • New Topic

B&S: until the desired resource becomes available...

Michael Cox
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Bodgitt and Scarper 2.1.1

"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."

I felt it was really bad to do this to a GUI user so my locking solution puts uses a lock request with a timeout. This puts the lock in a TIMED_WAIT rather than a WAIT state.

I'm pretty sure that consumes no CPU cycles but its not really blocking until the resource is available.

And of course now I'm about to submit and I'm in a flap about this.

Its says "should" rather than "must" which helps.

Does anyone have any good/bad experiences submitting this sort of approach?

If I had asked people what they wanted, they would have said faster horses - Ford. Tiny ad:
the new thread boost feature brings a LOT of attention to your favorite threads
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!