NAME

VERSION

SYNOPSIS

        # this is a simplistic example
        # you probably want to use L<JSON::RPC::Common::Marshal::Text> instead for
        # something like this.

        use JSON::RPC::Common::Procedure::Call;

        # deserialize whatever json text you have into json data:
        my $req = from_json($request_body);

        # inflate it and get a call object:
        my $call = JSON::RPC::Common::Procedure::Call->inflate($req);

        warn $call->version;

        # this will create a result object of the correct class/version/etc
        # "value" is the return result, regardless of version
        my $res = $call->return_result("value");

        # finally, convert back to json text:
        print to_json($res->deflate);

DESCRIPTION

This module does not concern itself with the transport layer at all, so the JSON-RPC 1.1 and the alternative specification, which are very different on that level are implemented with the same class.

RANT

Unfortunately it appears that JSON-RPC 1.1 is the most popular variant.

Since the client essentially chooses the version of the RPC to be used, for public APIs I reccomend that all versions be supported, but be aware that a 1.1-WD server "MUST" implement service description in order to be in compliance.

Anyway, enough bitching. I suggest making your servers 1.0+2.0, and your clients 2.0.

CLASSES

They are designed for high reusability. All the classes are transport and representation agnostic except for JSON::RPC::Common::Marshal::Text and JSON::RPC::Common::Marshal::HTTP which are completely optional.

TODO

• JSON::RPC::Common::Handler, a generic dispatch table based handler, useful for when you don't want to just blindly call methods on certain objects using "call" in JSON::RPC::Common::Procedure::Call.
• JSON::RPC::Common::Errors, a class that will provide dictionaries of error codes for JSON-RPC 1.1 and 1.1-alt/2.0.
• An object model for JSON-RPC 1.1 service description.

  SMD is required by most JSON-RPC 1.1 over HTTP clients.

  Since this is generally static, for now you can write one manually, see <http://groups.google.com/group/json-rpc/web/simple-method-description-for-json-rpc-example> for an example

• Moose class to SMD translator
• MooseX::Storage enabled objects can serialize themselves into JSON, and should DWIM when used. JSON-RPC 1.0 class hints could be used here too.
• Convert to Squirrel for smaller deps and faster load time. Need to find a solution for roles and type constraints. Neither is relied on heavily.

SEE ALSO

AUTHOR

COPYRIGHT AND LICENSE

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.