JSON-RPC Protocol: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "<B>Counter-Examples:</B>" to "<B>Counter-Example(s):</B>") |
m (Text replacement - "<B>Examples:</B>" to "<B>Example(s):</B>") |
||
Line 19: | Line 19: | ||
** It can support [[Security Layer]] for [[message protection]]. | ** It can support [[Security Layer]] for [[message protection]]. | ||
** ... | ** ... | ||
* <B> | * <B>Example(s):</B> | ||
** [[Protocol Version]]s, such as: | ** [[Protocol Version]]s, such as: | ||
*** [[JSON-RPC 1.0]] for [[basic rpc]]. | *** [[JSON-RPC 1.0]] for [[basic rpc]]. |
Latest revision as of 23:04, 28 December 2024
A JSON-RPC Protocol is a remote procedure call protocol that enables distributed systems to exchange procedure calls using json format.
- Context:
- It can establish Remote Communication through json messages.
- It can enable Method Invocation through request objects.
- It can support Result Handling through response objects.
- It can maintain Version Compatibility through protocol versions.
- It can handle Error States through error objects.
- ...
- It can often implement Batch Processing through request arrays.
- It can often provide Notification Handling through notification objects.
- It can often facilitate Service Discovery through method listings.
- It can often support Session Management through connection tracking.
- ...
- It can range from being a Simple JSON Message Protocol to being a Complex RPC Framework, depending on its implementation scope.
- It can range from being a Basic Data Exchange Protocol to being an Advanced Service Protocol, depending on its feature set.
- ...
- It can integrate with Transport Layer for message delivery.
- It can connect to Application Layer for service integration.
- It can support Security Layer for message protection.
- ...
- Example(s):
- Protocol Versions, such as:
- JSON-RPC 1.0 for basic rpc.
- JSON-RPC 2.0 for advanced features.
- Transport Implementations, such as:
- Message Types, such as:
- ...
- Protocol Versions, such as:
- Counter-Example(s):
- JSON REST Protocol, which uses resource-based architecture instead of procedure-based architecture.
- JSON Message Protocol, which lacks remote procedure call capabilities.
- JSON Schema Protocol, which validates data structures instead of executing procedures.
- See: Remote Procedure Call, JSON Format, Network Protocol, API Protocol, Service Protocol.