| Safe Haskell | None |
|---|---|
| Language | Haskell98 |
Network.Transport
Contents
Description
Network Transport
- data Transport = Transport {}
- data EndPoint = EndPoint {
- receive :: IO Event
- address :: EndPointAddress
- connect :: EndPointAddress -> Reliability -> ConnectHints -> IO (Either (TransportError ConnectErrorCode) Connection)
- newMulticastGroup :: IO (Either (TransportError NewMulticastGroupErrorCode) MulticastGroup)
- resolveMulticastGroup :: MulticastAddress -> IO (Either (TransportError ResolveMulticastGroupErrorCode) MulticastGroup)
- closeEndPoint :: IO ()
- data Connection = Connection {
- send :: [ByteString] -> IO (Either (TransportError SendErrorCode) ())
- close :: IO ()
- data Event
- type ConnectionId = Word64
- data Reliability
- data MulticastGroup = MulticastGroup {
- multicastAddress :: MulticastAddress
- deleteMulticastGroup :: IO ()
- maxMsgSize :: Maybe Int
- multicastSend :: [ByteString] -> IO ()
- multicastSubscribe :: IO ()
- multicastUnsubscribe :: IO ()
- multicastClose :: IO ()
- newtype EndPointAddress = EndPointAddress {}
- newtype MulticastAddress = MulticastAddress {}
- data ConnectHints = ConnectHints {}
- defaultConnectHints :: ConnectHints
- data TransportError error = TransportError error String
- data NewEndPointErrorCode
- data ConnectErrorCode
- data NewMulticastGroupErrorCode
- data ResolveMulticastGroupErrorCode
- data SendErrorCode
- data EventErrorCode
Types
To create a network abstraction layer, use one of the
Network.Transport.* packages.
Constructors
| Transport | |
Fields
| |
Network endpoint.
Constructors
| EndPoint | |
Fields
| |
data Connection Source #
Lightweight connection to an endpoint.
Constructors
| Connection | |
Fields
| |
Event on an endpoint.
Constructors
| Received !ConnectionId [ByteString] | Received a message |
| ConnectionClosed !ConnectionId | Connection closed |
| ConnectionOpened !ConnectionId Reliability EndPointAddress | Connection opened
|
| ReceivedMulticast MulticastAddress [ByteString] | Received multicast |
| EndPointClosed | The endpoint got closed (manually, by a call to closeEndPoint or closeTransport) |
| ErrorEvent (TransportError EventErrorCode) | An error occurred |
type ConnectionId = Word64 Source #
Connection data ConnectHintsIDs enable receivers to distinguish one connection from another.
data Reliability Source #
Reliability guarantees of a connection.
Constructors
| ReliableOrdered | |
| ReliableUnordered | |
| Unreliable |
Instances
data MulticastGroup Source #
Multicast group.
Constructors
| MulticastGroup | |
Fields
| |
newtype MulticastAddress Source #
EndPointAddress of a multicast group.
Constructors
| MulticastAddress | |
Fields | |
Hints
defaultConnectHints :: ConnectHints Source #
Default hints for connecting
Error codes
data TransportError error Source #
Errors returned by Network.Transport API functions consist of an error code and a human readable description of the problem
Constructors
| TransportError error String |
Instances
| Eq error => Eq (TransportError error) Source # | When comparing errors we ignore the human-readable strings |
| Show error => Show (TransportError error) Source # | |
| Generic (TransportError error) Source # | |
| (Typeable * err, Show err) => Exception (TransportError err) Source # | Although the functions in the transport API never throw TransportErrors (but return them explicitly), application code may want to turn these into exceptions. |
| Binary error => Binary (TransportError error) Source # | |
| type Rep (TransportError error) Source # | |
data NewEndPointErrorCode Source #
Errors during the creation of an endpoint
Constructors
| NewEndPointInsufficientResources | Not enough resources |
| NewEndPointFailed | Failed for some other reason |
Instances
data ConnectErrorCode Source #
Connection failure
Constructors
| ConnectNotFound | Could not resolve the address |
| ConnectInsufficientResources | Insufficient resources (for instance, no more sockets available) |
| ConnectTimeout | Timeout |
| ConnectFailed | Failed for other reasons (including syntax error) |
Instances
data NewMulticastGroupErrorCode Source #
Failure during the creation of a new multicast group
Constructors
| NewMulticastGroupInsufficientResources | Insufficient resources |
| NewMulticastGroupFailed | Failed for some other reason |
| NewMulticastGroupUnsupported | Not all transport implementations support multicast |
data ResolveMulticastGroupErrorCode Source #
Failure during the resolution of a multicast group
Constructors
| ResolveMulticastGroupNotFound | Multicast group not found |
| ResolveMulticastGroupFailed | Failed for some other reason (including syntax error) |
| ResolveMulticastGroupUnsupported | Not all transport implementations support multicast |
data SendErrorCode Source #
Failure during sending a message
Constructors
| SendClosed | Connection was closed |
| SendFailed | Send failed for some other reason |
Instances
data EventErrorCode Source #
Error codes used when reporting errors to endpoints (through receive)
Constructors
| EventEndPointFailed | Failure of the entire endpoint |
| EventTransportFailed | Transport-wide fatal error |
| EventConnectionLost EndPointAddress | We lost connection to another endpoint Although Network.Transport provides multiple independent lightweight connections between endpoints, those connections cannot fail independently: once one connection has failed, all connections, in both directions, must now be considered to have failed; they fail as a "bundle" of connections, with only a single "bundle" of connections per endpoint at any point in time. That is, suppose there are multiple connections in either direction between endpoints A and B, and A receives a notification that it has lost contact with B. Then A must not be able to send any further messages to B on existing connections. Although B may not realize immediately that its connection to A has been broken, messages sent by B on existing connections should not be delivered, and B must eventually get an EventConnectionLost message, too. Moreover, this event must be posted before A has successfully reconnected (in other words, if B notices a reconnection attempt from A, it must post the EventConnectionLost before acknowledging the connection from A) so that B will not receive events about new connections or incoming messages from A without realizing that it got disconnected. If B attempts to establish another connection to A before it realized that it got disconnected from A then it's okay for this connection attempt to fail, and the EventConnectionLost to be posted at that point, or for the EventConnectionLost to be posted and for the new connection to be considered the first connection of the "new bundle". |
Instances