AdvancedJsonRpc
Table of Contents
Classes
- Dispatcher
- Error
- ErrorCode
- The error codes from and including -32768 to -32000 are reserved for pre-defined errors. Any code within this range,
but not defined explicitly below is reserved for future use. The error codes are nearly the same as those suggested
for XML-RPC at the following url: http://xmlrpc-epi.sourceforge.net/specs/rfc.fault_codes.php
The remainder of the space is available for application defined errors.
- ErrorResponse
- When a rpc call is made, the Server MUST reply with a Response, except for in the case of Notifications. The Response
is expressed as a single JSON Object, with the following members:
- Message
- Base message
- Notification
- A Notification is a Request object without an "id" member. A Request object that is a Notification signifies the
Client's lack of interest in the corresponding Response object, and as such no Response object needs to be returned
to the client. The Server MUST NOT reply to a Notification, including those that are within a batch request.
- Request
- A rpc call is represented by sending a Request object to a Server
- Response
- When a rpc call is made, the Server MUST reply with a Response, except for in the case of Notifications. The Response
is expressed as a single JSON Object, with the following members:
- SuccessResponse
- When a rpc call is made, the Server MUST reply with a Response, except for in the case of Notifications. The Response
is expressed as a single JSON Object, with the following members: