Revert switch to jsonlite

This reverts commits deffc90, ab4dc64, and 0755579, returning to RJSONIO.
The purpose of this is to prepare for a maintenance release for 0.11
without the switch to jsonlite, to reduce the risk of new bugs.

man/registerInputHandler.Rd

@@ -16,7 +16,7 @@ parse the data delivered from the client before it is available in the
 parameters:
  \enumerate{
    \item{The value of this input as provided by the client, deserialized
-   using jsonlite.}
+   using RJSONIO.}
    \item{The \code{shinysession} in which the input exists.}
    \item{The name of the input.}
  }}
@@ -28,7 +28,7 @@ a handler defined.}
 \description{
 Adds an input handler for data of this type. When called, Shiny will use the
 function provided to refine the data passed back from the client (after being
-deserialized by jsonlite) before making it available in the \code{input}
+deserialized by RJSONIO) before making it available in the \code{input}
 variable of the \code{server.R} file.
 }
 \details{

man/removeInputHandler.Rd

@@ -15,7 +15,7 @@ The handler previously associated with this \code{type}, if one
 }
 \description{
 Removes an Input Handler. Rather than using the previously specified handler
-for data of this type, the default jsonlite serialization will be used.
+for data of this type, the default RJSONIO serialization will be used.
 }
 \seealso{
 \code{\link{registerInputHandler}}

man/session.Rd

@@ -84,7 +84,7 @@
 \item{sendCustomMessage(type, message)}{
   Sends a custom message to the web page. \code{type} must be a
   single-element character vector giving the type of message, while
-  \code{message} can be any jsonlite-encodable value. Custom messages
+  \code{message} can be any RJSONIO-encodable value. Custom messages
   have no meaning to Shiny itself; they are used soley to convey information
   to custom JavaScript logic in the browser. You can do this by adding
   JavaScript code to the browser that calls