network-transport: Network abstraction layer
|Versions||0.2.0, 0.2.0.1, 0.2.0.2, 0.3.0, 0.3.0.1, 0.4.0.0, 0.4.1.0, 0.4.2.0, 0.4.3.0, 0.4.3.1, 0.4.4.0, 0.5, 0.5.1, 0.5.2|
|Dependencies||base (>=4.3 && <5), binary (==0.5.*), bytestring (==0.9.*), transformers (>=0.2 && <0.4) [details]|
|Author||Duncan Coutts, Nicolas Wu, Edsko de Vries|
|Source repo||head: git clone https://github.com/haskell-distributed/distributed-process(network-transport)|
|Uploaded||by EdskoDeVries at Sat Jul 7 07:56:24 UTC 2012|
|Distributions||LTSHaskell:0.5.2, NixOS:0.5.2, Stackage:0.5.2, openSUSE:0.5.2|
|Downloads||13830 total (63 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
Network.Transport is a Network Abstraction Layer which provides the following high-level concepts:
Nodes in the network are represented by
EndPoints. These are heavyweight stateful objects.
Connections can be established from one
EndPointto another using the
EndPointAddressof the remote end.
EndPointAddresscan be serialised and sent over the network, where as
EndPoints and connections cannot.
EndPoints are unidirectional and lightweight.
Outgoing messages are sent via a
Connectionobject that represents the sending end of the connection.
Incoming messages for all of the incoming connections on an
EndPointare collected via a shared receive queue.
In addition to incoming messages,
EndPoints are notified of other
Events such as new connections or broken connections.
This design was heavily influenced by the design of the Common Communication Interface (http://www.olcf.ornl.gov/center-projects/common-communication-interface). Important design goals are:
Connections should be lightweight: it should be no problem to create thousands of connections between endpoints.
Error handling is explicit: every function declares as part of its type which errors it can return (no exceptions are thrown)
Error handling is "abstract": errors that originate from implementation specific problems (such as "no more sockets" in the TCP implementation) get mapped to generic errors ("insufficient resources") at the Transport level.
This package provides the generic interface only; you will probably also want to install at least one transport implementation (network-transport-*).
For package maintainers and hackage trustees