From mdowle at mdowle.plus.com  Fri Aug  7 08:43:16 2009
From: mdowle at mdowle.plus.com (Matthew Dowle)
Date: Fri, 7 Aug 2009 07:43:16 +0100
Subject: [Rd] Using svSocket with data.table
References: <h4eb3j$eji$1@ger.gmane.org> <1248555172-sup-4306@bloxx.local>
Message-ID: <h5gii5$2kc$1@ger.gmane.org>

Hi Olaf,

Thanks for your feedback, much appreciated.

> Don't be fooled. R does not handle multiple requests in parallel
> internally.
I wasn't fooled, but I've added some annotations to the video at the place
I might have given the impression I was (at 4min 39sec).  Later, at 
5min30sec I did already point out that the 'graph
stopped while the R server processed this clients request' but that is 
later.
http://www.youtube.com/watch?v=rvT8XThGA8o

> Also I suspect that, depending on what you do on the CLI, this will
> interact badly with svSocket.
Can you give an example to try out?

Regards, Matthew



"Olaf Mersmann" <olafm at kimberly.tako.de> wrote in message 
news:1248555172-sup-4306 at bloxx.local...
> Hi Matthew,
>
> Excerpts from Matthew Dowle's message of Sat Jul 25 09:07:44 +0200 2009:
>> So I'm looking to do the same as the demo,  but with a binary socket. 
>> Does
>> anyone have any ideas?  I've looked a bit at  Rserve, bigmemory, biocep, 
>> nws
>> but although all those packages are great,  I didn't find anything that
>> worked in exactly this way i.e.  i) R to R ii) CLI non-blocking and iii) 
>> no
>> need to startup R in a special way
>
> Don't be fooled. R does not handle multiple requests in parallel
> internally. Also I suspect that, depending on what you do on the CLI,
> this will interact badly with svSocket.
>
> As far as binary transfer of R objects goes, you are probably looking
> for serialize() and unserialize(). Not sure if these are guaranteed to
> work across differen versions of R and different word sizes. See the
> Warnings section in the serialize manual page.
>
> Cheers
> Olaf
>



[Rd] Using svSocket with data.table
Matthew Dowle