Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.ruby > #4817

Re: Another Couch potato question: Dealing with classic concurrency conflict

Show all headers | View raw

Robert K. wrote in post #999871:

> Well, if all your clients are Ruby programs you could of course
> implement the locking in Ruby e.g. by having a lock server process
> which is talked to via DRb.  All the tools you need for that are
> there: DRb for communication, Mutex and Monitor for locking.  Whether
> that's a good solution is a different cup of tea to answer. :-)

Hmmm... well I thought about that, and kind of hoped not to have to use
a lock server, but if I will have no other choice then using DRb is a
good idea, thanks!

>It's always a bit difficult to talk about these things on such a general
> level...

This is true. Hopefully, I will soon be able to share with the forum 
what I am doing and then I will be able to be more specific :-)
>
> Kind regards
>
> robert

-- 
Posted via http://www.ruby-forum.com/.

Back to comp.lang.ruby | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Another Couch potato question: Dealing with classic concurrency conflict Oren Shani <orenshani7@gmail.com> - 2011-05-20 05:50 -0500
  Re: Another Couch potato question: Dealing with classic concurrency conflict Robert Klemme <shortcutter@googlemail.com> - 2011-05-20 07:05 -0500
    Re: Another Couch potato question: Dealing with classic concurrency conflict Oren Shani <orenshani7@gmail.com> - 2011-05-20 08:11 -0500
      Re: Another Couch potato question: Dealing with classic concurrency conflict Robert Klemme <shortcutter@googlemail.com> - 2011-05-20 08:56 -0500
        Re: Another Couch potato question: Dealing with classic concurrency conflict Oren Shani <orenshani7@gmail.com> - 2011-05-20 09:28 -0500

csiph-web