From: Robert Klemme Date: 2005-04-29T00:09:28+09:00 Subject: Re: thread question "Peter Fitzgibbons" schrieb im Newsbeitrag news:7A813586612D444F9382A5B1288646F18CE64D@lakexch03.lakewoodhomes.net... > -----Original Message----- > From: Brian Schr�der [mailto:ruby.brian@gmail.com] > Sent: Monday, April 25, 2005 12:08 PM > To: ruby-talk ML > Subject: Re: thread question > > > On 25/04/05, Joe Van Dyk wrote: > > > On 4/25/05, Brian Schr�der wrote: > > > > On 25/04/05, Joe Van Dyk wrote: > > > > > Every second, a function in the class that's being made available > > > > > via DRb should be called automatically. How would I do that? > > > > One difference from your whish is, that this calls the function with a sleeptime of approximately one second, > or sometimes more, and not every second. Calling it every second is more difficult. > > > > Also, if I remember correctly, ruby threads may be blocked for some time by some large io activities. > > > > hope to help, > > > > Brian > > I hope that every programmer truly realizes that Win*, Mac* and *nix are NOT real-time-os. On all of these os', a second is not the standardized second, and the practical 'clock tick' is by no means absolutely a specific count of milliseconds. Although that's perfectly right I think Brian meant a different form of blocking: since Ruby threads are notn native, they will always block during long running functions because there is no preemption - even if system resources are plenty. The blocking you refer to is usually caused by some resource shortage where preemption by the OS's scheduler usually makes sure that every native thread get's its part of the time pie. Kind regards robert