svTaskCallbackManager {svSocket} | R Documentation |
svTaskCallbackManager()
is a copy of taskCallbackManager()
in
base package, as of version 2.9.2 of R. Two important differences: (1) the top
task created is named SV-taskCallbackManager
instead of
R-taskCallbackManager
, and its tasks are executed after each top-level
task in R console, or after execution of non-hidden R code from the socket
server (take care: only once per set of code, no mather the number of
top-level task in the R code send by the client in the second case). All
taskCallbacks defined by addTaskCallback()
or
taskCallbackManager$add()
from base package are not executed when code
is invoked from the R socket server!
svTaskCallbackManager(handlers = list(), registered = FALSE, verbose = FALSE)
handlers |
This can be a list of callbacks in which each element is a
list with an element named f which is a callback function, and an
optional element named data which is the 5-th argument to be supplied
to the callback when it is invoked. Typically this argument is not
specified, and one uses add to register callbacks after the manager is
created. |
registered |
A logical value indicating whether the evaluate
function has already been registered with the internal task callback
mechanism. This is usually FALSE and the first time a callback is
added via the add function, the evaluate function is automatically
registered. One can control when the function is registered by specifying
TRUE for this argument and calling addTaskCallback() manually. |
verbose |
A logical value, which if TRUE , causes information to
be printed to the console about certain activities this dispatch manager
performs. This is useful for debugging callbacks and the handler itself. |
See ?taskCallbackManager
for both the returned object and how to use it.
Slightly modified from the original function by the R core team
taskCallbackManager
, processSocket