The pipes-network-tls package
- 'ghc-options: -O2' is rarely needed. Check that it is giving a real benefit and not just imposing longer compile times on your users.
- Exposed modules use unallocated top-level names: Pipes
Use TLS-secured network connections together with the pipes ecosystem.
This package is organized using the following namespaces:
Pipes.Network.TCP.TLS exports pipes and utilities for using TLS-secured TCP connections in a streaming fashion.
Pipes.Network.TCP.TLS.Safe subsumes Pipes.Network.TCP.TLS, exporting pipes and functions that allow you to safely establish new TCP connections within a pipeline using the pipes-safe facilities. You only need to use this module if you want to acquire and release operating system resources within a pipeline.
See the NEWS file in the source distribution to learn about any important changes between version.
[Skip to ReadMe]
|Versions||0.1.0.0, 0.1.1.0, 0.2.0, 0.2.0, 0.2.1|
|Dependencies||base (==4.*), bytestring (>=0.9.2.1), network, network-simple (==0.3.*), network-simple-tls (==0.2.*), pipes (==4.0.*), pipes-network (==0.6.*), pipes-safe (==2.0.*), tls (==1.1.*), transformers (>=0.2 && <0.4) [details]|
|Copyright||Copyright (c) Renzo Carbonara 2013|
|Source repository||head: git clone git://github.com/k0001/pipes-network-tls.git|
|Uploaded||Fri Oct 4 21:55:22 UTC 2013 by RenzoCarbonara|
- pipes-network-tls-0.2.0.tar.gz [browse] (Cabal source package)
- Package description (included in the package)
For package maintainers and hackage trustees