Ruby interpreter thread safety

[Thomas Sondergaard]

I have a scenario where a ruby extension module starts real/os/heavy-weight
threads that may call back to ruby. As far as I understand the ruby
interpreter itself is not thread safe. How can I handle this thread-safety
problem?

Cheers,

Thomas

 

[nobu.nokada]

Hi,

At Thu, 4 Sep 2003 19:45:24 +0900,

I have a scenario where a ruby extension module starts real/os/heavy-weight
threads that may call back to ruby. As far as I understand the ruby
interpreter itself is not thread safe. How can I handle this thread-safety
problem?

Run the ruby interpreter in a particular os-thread, and use
system provided queue.

 

[Jim Weirich]

I have a scenario where a ruby extension module starts real/os/heavy-weight
threads that may call back to ruby. As far as I understand the ruby
interpreter itself is not thread safe. How can I handle this thread-safety
problem?

The general solution for any threaded code making calls to a non-thread
safe library is to do one of the following:

(a) Make calls into the library (callbacks in your case) from
only a single thread.
or (b) Serialize calls to the library by using a mutex of some type.

 

[Thomas Sondergaard]

The general solution for any threaded code making calls to a non-thread

safe library is to do one of the following:

(a) Make calls into the library (callbacks in your case) from
only a single thread.
or (b) Serialize calls to the library by using a mutex of some type.

Got it!

Thomas

 

[Thomas Sondergaard]

Run the ruby interpreter in a particular os-thread, and use
system provided queue.

Could you give me an example of such a system provided queue?

Cheers,

Thomas