Allowed soap_v2 style request in JSON-RPC and added event 'api_server_adpter_jsonrpc_run_after'

[kiatng]

…pter_jsonrpc_run_after'

Description (*)

This allows soap_v2 style:

$client = new Krixon_JsonRpc_Client($url);
//...
$result = $client->call('magento.info', [$sessionId]); // v2 style
$result = $client->call('call', [$sessionId, 'magento.info', []]); // v1 style

A new event 'api_server_adapter_jsonrpc_run_after' is added. This is useful to log incoming requests and responses.

In one of my projects, I have custom APIs which I need to provide documentation with. I find v2 style is easier for the clients. In v1 style, the method/procedure is always call(), the name of the actual procedure is in the params. In v2 style, it makes more sense because as the name RPC implies, the client call the procedure by name.

[colinmollenhour]

Surely the JSONRPC adapter is not already in heavy use, perhaps this should be the only way and not an alternative to avoid higher burdens of documentation for the inferior method?

[kiatng]

Surely the JSONRPC adapter is not already in heavy use, perhaps this should be the only way and not an alternative to avoid higher burdens of documentation for the inferior method?

For people who want to migrate from SOAP(v1&v2)/XML to JSON-RPC, it's easier for the client if we accept both v1 and v2 style.

[colinmollenhour]

Makes for a very clean API! Nice job!👍