FastRWeb - Fast Interactive Web Framework for Data Mining Using R
Package R docs
1.1-1 (under development)
o clear the output buffer before serving run() scripts
o using out() on WebPlots will now use dataURI instead
of temporary files
o The interface to the R process has been enhanced to support
request body and other methods including POST. A new global
variable `request' is a list that is populated with various
entries pertinent to the request:
request$uri - URI of the request (used to be request.URI)
request$method - method type (as string) such as "GET"
request$c.type - content type of the request body
request$c.length - length of the request body (-1 if
there is no body)
request$body - raw vector containing the body of the request
request$client.ip - IP address of the client (as string)
request$raw.cookies - raw cookie string
request$path.info - path part beyond the script name
All strings are guaranteed to be "" if not set.
request$body will be NULL if there is no body.
o The interface to the R process now sets a global variable
`webapi` which is a real number that defines the version of
the interface used to pass information. It is now set to 1.1
and guarantees the information described above. This number
will be increased in case new features are added to the API
between the R process and the web server.
o FastRWeb now provides an internal `.run()' function which does
the necessary processing of a request, so additional
FastRWeb-compliant front-ends are easy to implement by simply
creating the request structure and calling the `.run()'
o FastRWeb contains an experimental .http.request()
implementation which can be used with Rserve's HTTP server,
removing all middle layers - no webserver, CGI or PHP is needed.
Simply evaluate `.http.request <- FastRWeb:::.http.request`
during Rserve startup.
o FastRWeb now attempts to parse known content types - not just
the query string but also "application/x-www-form-urlencoded"
and multi-part encodings. If the key name is used, query
string has higher precedence. It is still possible to separate
the various types by hand from request$body, for multipart
content content FastRWeb now provides parse.multipart()
function (courtesy of Jeff Horner).
o Rcgi will respond with appropriate status code to various
error conditions, such as failed connection. Previously, Rcgi
would always respond with 200 OK.
o Rcgi bugfix: the parameter sanitization code was behaving
o Rcgi has been updated to switch to binary stdout for file and
tmpfile on Windows, otherwise binary data (like images) will
arrive malformed at the webserver when running FastRWeb on
Windows (thanks to Francois Guillem for reporting and
o clean up quoting inside attributes in o* tools
o added oclear() to re-set output and/or headers
o Parameters to run() were passed in URL-encoded form - that was
a bug. They are now passed in decoded form as intended.
WARNING: if you worked around this bug in your scripts for
FastRWeb 1.0 make sure you remove the work around for
FastRWeb 1.1 and higher (check for the presence of webapi
if you need to support both).
o added rudimentary form elements constructors:
oinput(), oselection() and osubmit()
o some S3 methods were not registered in the namespace
o CRAN release
o add examples and tmp.R implementation
o add support for headers manipulation
o add sample project root configuration
and install.sh for installation
o add WebResult and WebPlot classes
o first public version