The yaml-rpc package

[Tags:bsd3, library]

This library aimed to organize remote procedure call (RPC) over TCP/IP network, using YAML as data serialization format.

[Skip to Readme]


Versions 0.1, 0.2, 0.3, 0.3.1, 1.0, 1.0.1, 1.0.2, 1.0.3
Dependencies base (>=3 && <=5), bytestring, containers, convertible-text, data-default, data-object, data-object-yaml, mtl, network, random, template-haskell, yaml [details]
License LGPL-3
Author Ilya V. Portnov
Category Network
Home page
Uploaded Sun May 30 11:43:28 UTC 2010 by IlyaPortnov
Distributions NixOS:1.0.3
Downloads 1459 total (15 in the last 30 days)
0 []
Status Docs not available [build log]
All reported builds failed as of 2016-12-30 [all 7 reports]
Hackage Matrix CI


  • Network
    • Network.YAML
      • Network.YAML.Balancer
      • Network.YAML.Base
      • Network.YAML.Caller
      • Network.YAML.Derive
      • Network.YAML.Dispatcher
      • Network.YAML.Instances
      • Network.YAML.Server
      • Network.YAML.WrapMethods


Maintainer's Corner

For package maintainers and hackage trustees

Readme for yaml-rpc

Readme for yaml-rpc-0.2

Ilya V. Portnov <>

The yaml-rpc package contains a small library to organize remote procedure call
(RPC) over TCP/IP network, using YAML as data serialization format.

RPC server should supply a set of "RPC methods", which are simply functions ::
a -> IO b, `a' and 'b' should be of class IsYamlObject. This class guarantees
that values of given type can be serialized to YAML and de-serialized.
Network.YAML.Instances module provides some instances declaration for this
typeclass. Moreover, Network.YAML.Derive module contains (TemplateHaskell)
function deriveIsYamlObject, which will help you to declare `instance
IsYamlObject ...' for almost any ADT.

RPC-client calls RPC-methods usually using one of two ways. First is to use
`call' (or `callDynamic') function from Network.YAML.Caller module. One need to
give method name as it's parameter. Second way is to use (TemplateHaskell-)
function `remote' from Network.YAML.WrapMethods module to declare wrapper
functions for RPC-methods. These wrappers will have same names as source
functions, and almost same behaivour. Single difference is that wrappers
require pair: (RPC-server host name, port number) as their first argument.

You can see examples of usage in files Test.hs and TestCall.hs. Haddock
documentation is here:

Depends: ghc >= 6.10, network, data-object, data-object-yaml, yaml,
data-default, convertible-text.