Hi,

> From: Brian Candler [mailto:B.Candler / pobox.com] 
> Sent: Tuesday, March 11, 2003 6:08 AM

> Something to beware of with Ruby implementations of both DRb 
> and SOAP server (and possibly others) is their interaction
> with threading. In both cases, you pass a single object to
> the server, and it listens for requests: but each time it
> answers a request, it start a *new thread* for the method call
> but on the *same object* whilst continuing to accept new 
> inbound requests.

Regards to soap4r, it depends on server side implementation.
Using soaplet.rb with WEBrick, you can use
SOAPlet#addRequestServant to add 'Request scope' object,
SOAPlet#addServant to add 'Application scope' object.

# No 'Session scope' object for now.

dRuby is from 'Distributed Ruby', and the author Seki-san
intends to offer users to be able to move in-process Ruby
environment to distributed Ruby environment easily.  No one
expect

  s = Servant.new
  5.times do
    res = s.request
  end

to do s.dup for each request.  So users who want mutex,
ACL, name service, activation and etc which Ruby does not need,
creates these by themself.

# Fortunately there are many samples around dRuby.
# Rinda::Ring as lightweight Jini, etc.

Regards,
// NaHi