[rkward-cvs] SF.net SVN: rkward:[3277] branches/jss_dec_10/FINAL_JSS_TEX/technical.tex

tfry at users.sourceforge.net tfry at users.sourceforge.net
Mon Dec 20 12:00:27 UTC 2010

Revision: 3277
Author:   tfry
Date:     2010-12-20 12:00:27 +0000 (Mon, 20 Dec 2010)

Log Message:
Change figure text.
@Stefan, Note that running on separate machines (not just separate processes) is not possible, yet, and cannot be done in the short term.
So I'm not comfortable with giving too much detail on that vision, yet.

Modified Paths:

Modified: branches/jss_dec_10/FINAL_JSS_TEX/technical.tex
--- branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-20 11:25:54 UTC (rev 3276)
+++ branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-20 12:00:27 UTC (rev 3277)
@@ -50,10 +50,10 @@
  \caption{Technical design of RKWard. Only a few central components are visualized.
-Plugins are defined by the RKWard developers or by the user.
-RKWard takes care of correct \proglang{R} script processing (e.g. loading of packages, data loading) as defined by the plugin.
-The asynchronous threaded design (Section~\ref{sec:technical_asynchronous}) do not require R and RKWard to run on the same Computer.
-For example one RKWard developer runs \proglang{R} on a RHEL\footnote{\url{http://www.redhat.com/rhel/}} (With Red Hat Enterprise Linux) server, whereas RKWard runs on a Debian\footnote{\url{http://www.debian.org/releases/unstable/}} unstable client.}
+ All communication with the R engine is passed through a single interface living in the main application thread. The R engine itself
+ runs in a separate thread (or in a separate process). 
+ Separate threads are also used to generate \proglang{R} code from plugins.

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

More information about the rkward-tracker mailing list