1JSON::RPC::Common::ProcUesdeurreC:oJ:nSCtOarNli:lb::uR:tPVeCed:r:sPCieoormnlm_o1Dn_o:1c:(uP3mr)eoncteadtuiroen::Call::Version_1_1(3)
2
3
4

NAME

6       JSON::RPC::Common::Procedure::Call::Version_1_1 - JSON-RPC 1.1
7       Procedure Call
8

SYNOPSIS

10               use JSON::RPC::Common::Procedure::Call;
11
12               my $req = JSON::RPC::Common::Procedure::Call->inflate({
13                       version => "1.1",
14                       id      => "oink",
15                       params  => { foo => "bar" },
16               });
17

DESCRIPTION

19       This class implements JSON-RPC 1.1 Procedure Calls according to the 1.1
20       working draft: http://json-rpc.org/wd/JSON-RPC-1-1-WD-20060807.html
21       <http://json-rpc.org/wd/JSON-RPC-1-1-WD-20060807.html>.
22
23       JSON RPC 1.1 requests are never notifications, and accept either hash
24       references or array references as parameters.
25
26       Note that the alternative JSON RPC 1.1 proposition is also be
27       supported: http://groups.google.com/group/json-rpc/web/json-rpc-1-1-alt
28       <http://groups.google.com/group/json-rpc/web/json-rpc-1-1-alt>.
29       "kwparams" is accepted as an alias to "params", but "params" will also
30       accept hash references. However, to simplify things, "params" and
31       "kwparams" are mutually exclusive, since Perl doesn't have strong
32       support for named params.
33
34       The alternative spec does not offer notifications (it is a TODO item),
35       so currently "is_notification" always returns false.
36
37
38
39perl v5.12.0                JSON::2R0P0C9:-:0C7o-m0m2on::Procedure::Call::Version_1_1(3)
Impressum