run.Rserve

all named arguments are treated as entries that would be otherwise
    present in the configuration file. So argument <code>foo="bar"</code>
    has the same meaning as <code>foo bar</code> in the configuration
    file. The only exception is that logical

path of the configuration file to load in the Rserve. It will be
    loaded before the above settings and is optional, i.e. if the
    file is not present or readable it will be ignored.

config.file

<code>run.Rserve</code> makes the current R process into an Rserve
  instance. Rserve takes over until it is shut down or receives a user
  interrupt signal. The main difference between <code><a href="/link/Rserve?package=Rserve&version=1.7-2" rd-options="" data-mini-rdoc="Rserve::Rserve">Rserve</a></code> and
  <code>run.Rserve</code> is that <code>Rserve</code> starts a new process, whereas
  <code>run.Rserve</code> turns the current R session into Rserve. This is only
  possible if there are no UI elements or other parts that could
  interfere with the prepation of <code>Rserve</code>.

interface

Rserve acts as a socket server (TCP/IP or local sockets) 
	     which allows binary requests to be sent to R. Every
	     connection has a separate workspace and working
	     directory. Client-side implementations are available
	     for popular languages such as C/C++ and Java, allowing
	     any application to use facilities of R without the need of
	     linking to R code. Rserve supports remote connection,
	     user authentication and file transfer. A simple R client
	     is included in this package as well.

run.Rserve: Start Rserve within the current R process.

Description

Usage

Arguments

Value

See Also