2008/1/18, Barry Rowlingson <[EMAIL PROTECTED]>:
> richard mendes wrote:
>
> > The question i have is how does rpy handle multithreads.
> >
> > What i've seen till now is that a r object is created when importing
> > the rpy library. how does this react to multithreads.
>
> Those are fairly vague
R itself is neither multithreaded, nor thread safe. If you want to
interact with more than one R session, you'll have to have a separate
process for each R session. I built the RSOAP tool, which includes
wrapper (called something like) LocalRSOAPConnection that wraps the
separate session
thanks a lot,
this give's me some more info i can use in determining the architecture.
I will certainly look into the option os.fork.
Richard
On 1/18/08, Barry Rowlingson <[EMAIL PROTECTED]> wrote:
> richard mendes wrote:
>
> > The question i have is how does rpy handle multithreads.
> >
> > W
richard mendes wrote:
> The question i have is how does rpy handle multithreads.
>
> What i've seen till now is that a r object is created when importing
> the rpy library. how does this react to multithreads.
Those are fairly vague questions, so I'll answer the specifics:
> Is that r object
Hello Rpy Users,
Last few days i've been looking into a interaction between python and
.The company i work for currently uses rserve to connect to R. Based
on the features of rpy we decided we implement a new interface that
library.
The question i have is how does rpy handle multithreads.
What i
