sockets: High-level network sockets
This library provides a high-level abstraction for network sockets. It uses Haskell2010 (along with GADTs) without typeclasses to ensure that consumers of the API can only call appropriate functions on a socket.
Exceptions are tracked in the types of functions and returned to the caller
Either. The caller is free to handle these gracefully or to throw
them. This library has another class of exceptions described as _unrecoverable_.
This library only throws exceptions in three situations:
The library detects that it has misused the operating system's sockets API. This includes getting a
sockaddrwith an unexpected socket family. It also includes getting an error code that should not be possible. For example, the abstractions provided for both datagram sockets and stream sockets mean that
sendsystem calls in either context should never return the error code
ENOTCONN. Consequently, this error is treated as unrecoverable.
The caller asks for a negatively-sized slice of a buffer (such exceptions indicate a mistake in the code consuming this API).
A system call fails with
ENOMEM. These indicate that the operating system is out of memory. If this happens, the Out Of Memory (OOM) manager is likely killing processes to reclaim memory, so the process that received this message may be killed soon. Making things even worse is that the GHC runtime requests pages of memory from the operating system at times that are effectively unpredictable to Haskell developers. (Most memory-managed languages have this behavior). Any attempt to recover from
ENOMEMmight cause the runtime to allocate memory from the operating system. According to the documentation for the HeapOverflow exception, an allocation failure at this point in time (likely given the recent
ENOMEM) would result in immidiate termination of the program. So, although it is technically possible to recover from
ENOMEM, the OOM killer and the GHC runtime make it impossible to do so reliably. Consequently, these error codes are treated as fatal.
|Versions [faq]||0.1.0.0, 0.3.0.0, 0.3.1.0, 0.4.0.0, 0.5.0.0|
|Dependencies||base (>=184.108.40.206 && <5), byteslice (>=0.1.1 && <0.2), bytestring (==0.10.*), error-codes (>=0.1.0.1 && <0.2), ip (>=1.4.1), posix-api (>=0.3.2 && <0.4), primitive (==0.7.*), primitive-addr (==0.1.*), primitive-offset (==0.2.*), primitive-unlifted (==0.1.*), stm (>=2.4), text (>=1.2) [details]|
|Copyright||2019 Andrew Martin|
|Revised||Revision 1 made by andrewthad at 2019-07-21T20:09:43Z|
|Uploaded||by andrewthad at 2019-07-21T19:38:37Z|
|Downloads||1513 total (48 in the last 30 days)|
|Rating||(no votes yet) [estimated by Bayesian average]|
Docs not available [build log]
All reported builds failed as of 2019-07-21 [all 3 reports]
Use sendmmsg and recvmmsg
More informative messages from internal errors
Print debug output
Add bounds-checking to primitive array operations
Build example executables
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
- sockets-0.5.0.0.tar.gz [browse] (Cabal source package)
- Package description (revised from the package)
Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.
For package maintainers and hackage trustees