4 ms·
Still using JSON-RPC 1.0 over HTTP here: - specs so simple it's incredibly easy to implement client and server in most languages - good enough for most use
by JodieBenitez 4y ago
Still using JSON-RPC 1.0 over HTTP here:
- specs so simple it's incredibly easy to implement client and server in most languages
- good enough for most use case, supports whatever that can be expressed in JSON
- easy enough to inspect, it's just JSON
- not too heavy compared to XML-RPC
- as performant as your JSON serializer/deserializer
- None of the ReSTish philosophical questionings
- understood by developers of any generation: call methods with parameters
- to11mtm 4y agoalso: > - None of the ReSTish philosophical questionings Adding to this, - If you ever -do- need to drop to something else (i.e. GRPC, websockets) you're not having to re-translate all of your restishness into commands.
- jiggawatts 4y agoSimple my arse: https://news.ycombinator.com/item?id=16897061 https://news.ycombinator.com/item?id=16897061 JSON, especially for multi-hop RPC, is a minefield of security and compatibility issues because the spec is too simple in a way, making it very complicated to handle safely and securely.