authorize: Authorize further message processing

In jrc: Exchange Commands Between R and 'JavaScript'

Authorize further message processing

Description

jrc library allows one to get full control over the currently running R session from a web page. Therefore for security reasons one should manually authorize function calls, variable assignments or expression evaluations. All the received messages that are not processed automatically are given an ID and stored. This function allows a message with the given ID to be evaluated. It can also show a short description of the message and give user a choice between running it or discarding.

Usage

authorize(sessionId = NULL, messageId = NULL, show = FALSE)

Arguments

sessionId	ID of the session that received the message. If there is only one active session, this argument becomes optional.
messageId	ID of the message to be processed. If the session has only one stored message, this argument becomes optional.
show	If TRUE information about the message will be shown first. After that user gets a choice to go on with evaluation, to ignore the message (meaning it will be removed from memory) or to do nothing.

Details

Expressions has to be always authorized before evaluation. One can specify a list of variables that can be changed automatically and functions that can be called without authorization.

This function is a wrapper around authorize method of class Session.

See Also

allowFunctions, allowVariables, setLimits, getSessionIds, getMessageIds.

Examples

## Not run: 
# to run this example an installed web browser is required
openPage()

callFunction("jrc.sendCommand", list("k <<- 10"), wait = 1)
allowVariables("x")
callFunction("jrc.sendData", list("x", 15), wait = 1)
callFunction("jrc.sendData", list("y", 20), wait = 1)
msgId <- getMessageIds()
authorize(messageId = msgId[1])
#run that to first see some information about the message
#authorize(messageId = msgId[2], show = TRUE)

closePage()
## End(Not run)

jrc documentation built on Aug. 23, 2023, 5:10 p.m.