rotocol for requesting metadata and performing actions on code entities.
Examples are written in JSON (sometimes with added comments), but data
structures can actually be encoded using other formats. 1.2 (Oct 2014)
Version bumped to 1.2. This version addresses sending/receiving binary data over
JSON. In this version, client can send base64-encoded binary data in arguments
using C<ARGNAME:base64>ase of L<Sub::Spec::HTTP::Server>.
=head1 SEE ALSO
L<Rinci>
JSON RPC, (version 1 at L<http://json-rpc.org>, version 2 at
L<http://jsonrpc.org>). First developed 2005, major revision to version 2 inIt supports less
features (currently only supports sending/receiving Riap request and response in
JSON encoding, no encryption, no authentication, no sending of logging
messages). It is suitable for lhe following format:
"j" <JSON> <CRLF>
That is, the lowercase letter C<j> followed by JSON data (must all be in one
line), followed by CRLF.
=head2 Response
"j" <JSON> <CRLF>
That is, the lowercase letter C<j> followed by enveloped result encoded in JSON
(will all be in one line) and a single <CRLF>. The next request can then be sent
by client.
If client/server sends an invalid request/rese decided by the
implementation, but server MUST support C<json> as the fallback. If unspecified,
default in most cases should also be C<json>, but server can default to other
format, like say L<HTML>rializations are supported, client can perform an C<srvinfo>
action.
Server should fallback to C<json> if requested result format is not supported.
=back
=head2 Additional actions
=head3 Action: Bl": "http://localhost:5000/",
// supported formats
"fmt": ["Console","HTML","JSON","PHPSerialization","YAML","json"],
}
=head2 Parsing Riap request from HTTP request
Server can provide default