Module documentation for 0.6.4
There are no documented modules for this package.
Utilities to deal with sockets using the pipes and pipes-safe libraries.
Check the source or rendered Haddocks for extensive documentation.
This code is licensed under the terms of the so called 3-clause BSD
license. Read the file named
LICENSE found in this same directory
PEOPLE file to learn about the people involved in this
Raise upper-bound dependency on
Pipes.Network.TCP.Safenow close the listening socket immediately after accepting a first connection.
Fix issue #29 where
fromSocketTimeoutNwould loop forever.
Base m ~ IOconstraints from
Pipes.Network.TCP.Safe, as not all of them were removed in 0.6.1.
Dependency bumps (upper bounds).
Base m ~ IOconstraint from
Significantly upgraded the API and renamed functions to play well with pipes-4.0.0, pipes-safe-2.0.0 and network-simple-0.3.0.
IOin order to report timeout errors. Delete the
recvas eported by network-simple-0.2.1.0.
acceptForknow properly closes the connection socket, even in case of asynchronous exceptions.
Do not handle “Broken Pipe” errors on the
*Write*Dproxies anymore. As as a result, those proxies run forever and have a polymorphic return value, which makes this release binary compatible with 0.2.0.0, but not with 0.3.0.0.
Quietly stop writing or reading bytes from a TCP socket if a “Broken Pipe” error happens, indicating that the remote end already closed the connection. Previously, a
ResourceVanishedexception was thrown.
*Write*Dproxies now return
()if the remote end closed the connection.
Depend on network-simple 0.2
In both modules
serveForkwas renamed to
serveand the previous function named
- Split many of the non-pipes-related TCP utilities to the own
- Depend on
network-simpleand re-export its functions.
- New backwards incompatible API
- Based on pipes 3.1
Up to version 0.0.2
- Based on pipes-core.