Hackage :: [Package]

json-rpc: Fully-featured JSON-RPC 2.0 library

[ library, mit, network, program, public-domain ] [ Propose Tags ] [ Report a vulnerability ]

Please see the README on GitHub at https://github.com/jprupp/json-rpc#readme

[Skip to Readme]

Modules

[Index] [Quick Jump]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.1.0.0, 0.1.0.1, 0.1.0.2, 0.1.0.3, 0.1.0.4, 0.1.0.5, 0.2.0.0, 0.2.0.1, 0.2.0.2, 0.2.1.0, 0.2.1.1, 0.2.1.2, 0.2.1.4, 0.2.1.5, 0.2.1.6, 0.3.0.0, 0.3.0.1, 0.3.0.2, 0.4.0.0, 0.5.0.0, 0.6.0.0, 0.6.1.0, 0.6.2.0, 0.6.2.1, 0.7.0.0, 0.7.0.1, 0.7.0.2, 0.7.1.0, 0.7.1.1, 0.8.0.0, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1
Change log CHANGELOG.md
Dependencies aeson, attoparsec, attoparsec-aeson, base (>=4.6 && <5), bytestring, conduit, conduit-extra, deepseq, hashable, json-rpc, monad-logger, mtl, QuickCheck, stm-conduit, text, time, unliftio, unordered-containers, vector [details]
License MIT
Author Jean-Pierre Rupp
Maintainer jprupp@protonmail.ch
Category Network
Home page https://github.com/jprupp/json-rpc.git#readme
Bug tracker https://github.com/jprupp/json-rpc.git/issues
Source repo head: git clone https://github.com/jprupp/json-rpc.git
Uploaded by jprupp at 2024-03-14T12:54:55Z
Distributions LTSHaskell:1.1.1, Stackage:1.1.1
Reverse Dependencies 5 direct, 0 indirect [details]
Executables time-server, time-client, concurrent-server, concurrent-client
Downloads 23479 total (18 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]

Readme for json-rpc-1.1.1

[back to package description]

json-rpc

Fully-featured JSON-RPC 2.0 library for Haskell programs.

This JSON-RPC library is fully-compatible with JSON-RPC 2.0 and 1.0. It provides an interface that combines a JSON-RPC client and server. It can set and keep track of request ids to parse responses. There is support for sending and receiving notifications. You may use any underlying transport. Basic TCP client and server provided.

A JSON-RPC application using this interface is considered to be peer-to-peer, as it can send and receive all types of JSON-RPC message independent of whether it originated the connection.

Documentation

Examples