Question 1

How to add authentication to osamingo/jsonrpc?

Accepted Answer

Authentication isn't built-in; you need to implement it using Go's standard HTTP middleware or frameworks like chi. Wrap the MethodRepository handler to check credentials before processing JSON-RPC requests.

Question 2

osamingo/jsonrpc vs gRPC for Go: which should I use?

Accepted Answer

Choose jsonrpc for human-readable JSON over HTTP, ideal for web compatibility and simplicity. gRPC is better for performance-critical applications with binary encoding and strong type safety via Protocol Buffers.

Question 3

How to handle custom errors in jsonrpc methods?

Accepted Answer

Use the jsonrpc.Error type to return standard error responses. Define custom error codes and messages in your handlers by implementing the error interface, ensuring compliance with the JSON-RPC spec.

Question 4

Can I use jsonrpc with frameworks like Gin or Echo?

Accepted Answer

Yes, integrate it by treating the MethodRepository as an http.Handler. Set up routes in your framework to forward requests to the repository, similar to the standard net/http example in the README.

Question 5

How to test JSON-RPC endpoints built with this package?

Accepted Answer

Write unit tests for your handlers using Go's testing package. Use net/http/httptest to simulate HTTP requests and validate responses, ensuring method registration and parameter parsing work correctly.

Question 6

Does osamingo/jsonrpc support batch requests?

Accepted Answer

JSON-RPC 2.0 supports batch requests, and the package should handle them, but check the godoc or source code for implementation details, as the README doesn't explicitly demonstrate batch processing.

jsonrpc

What is jsonrpc?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions