Personal tools

Pipes

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
m
 
(3 intermediate revisions by 3 users not shown)
Line 127: Line 127:
   
 
* [https://groups.google.com/d/msg/haskell-pipes/7I8KcMW3zHU/5Mi8PKbuv2sJ pipes-binary-0.1.0.0]: Encode and decode binary streams using the <code>binary</code> package.
 
* [https://groups.google.com/d/msg/haskell-pipes/7I8KcMW3zHU/5Mi8PKbuv2sJ pipes-binary-0.1.0.0]: Encode and decode binary streams using the <code>binary</code> package.
  +
  +
* [http://www.haskellforall.com/2013/09/pipes-40-simpler-types-and-api.html pipes-4.0.0]: Simpler types and API
   
 
== Upcoming libraries ==
 
== Upcoming libraries ==
Line 133: Line 135:
   
 
* pipes-text: Text support
 
* pipes-text: Text support
  +
  +
== Videos ==
  +
  +
* [http://www.youtube.com/watch?v=2jdJGdA7AYs Pipes], by Oliver Charles. London Haskell user group, 18th September 2013.
  +
  +
== See also ==
  +
  +
* [http://www.yesodweb.com/blog/2013/10/core-flaw-pipes-conduit The core flaw of pipes and conduit] (blog article)

Latest revision as of 22:22, 23 October 2013


The pipes library is a clean and powerful stream processing library that lets you build and connect reusable streaming components.

Contents

[edit] 1 Libraries

Pipes is the official Hackage category for the pipes ecosystem.

[edit] 1.1 pipes

The pipes package is the core library which provides reusable primitives for stream programming. Use these as building blocks for more sophisticated streaming abstractions.

Read the official pipes tutorial to learn more.

Source code hosted on GitHub

[edit] 1.2 pipes-safe

The pipes-safe package adds resource management and exception safety to the pipes ecosystem. Use pipes-safe to safely acquire and release resources deterministically within a pipeline.

Source code hosted on GitHub

[edit] 1.3 pipes-concurrency

The pipes-concurrency package adds concurrency primitives to the pipes ecosystem with built-in deadlock safety. Use these primitives to:

  • Build reactive event-driven programs
  • Merge and broadcast streams
  • Communicate between multiple concurrent pipelines

Read the official pipes-concurrency tutorial to learn more.

Source code hosted on GitHub

[edit] 1.4 pipes-parse

The pipes-parse package defines the generic machinery necessary for common parsing tasks. Use pipes-parse to:

  • handle leftovers and end of input,
  • interrupt and resume streaming, and
  • sub-divide streams without collecting elements in memory.

Source code hosted on GitHub

[edit] 2 Community-contributed libraries

Listed in alphabetical order.

[edit] 2.1 pipes-aeson

The pipes-aeson library allows you to encode and decode JSON values flowing through streams, possibly interleaving other stream effects while doing it.

Source code is hosted on GitHub

[edit] 2.2 pipes-attoparsec

The pipes-attoparsec library converts attoparsec parsers to pipes for high-performance incremental parsing.

Source code hosted on GitHub

[edit] 2.3 pipes-binary

The pipes-binary library allows streams of binary data to be encoded and decoded using the Binary instances from the binary package.

Source code is hosted on GitHub

[edit] 2.4 pipes-network

The pipes-network library converts server and client sockets to pipes to seamlessly stream data over any network.

Source code hosted on GitHub

[edit] 2.5 pipes-network-tls

The pipes-network-tls allows streaming through TLS-secured network connections, exposing a similar API to the one exposed by pipes-network.

Source code hosted on GitHub

[edit] 2.6 pipes-zlib

The pipes-zlib enables compression and decompression of strict ByteString streams using the zlib codec.

Source code hosted on GitHub

[edit] 3 Community

Besides the usual Haskell community channels such as the official mailing lists or the Haskell subreddit, you can ask for help, suggest improvements, or discuss about the Pipes ecosystem at the “haskell-pipes” mailing list at Google Groups.

[edit] 4 Announcements

In chronological order:

  • pipes-1.0.0: The original announcement, which first introduced the concept of unifying sources and sinks and transducers into a single Category.
  • pipes-2.0.0: The introduction of Frames, later deprecated in favor of pipes-safe.
  • pipes-2.1.0: Transition of Frames to indexed monads, later deprecated in favor of pipes-safe.
  • pipes-2.3.0: The introduction of bidirectional Proxies, which evolved into modern pipes.
  • pipes-2.4.0: The release of the proxy transformer extension system.
  • pipes-3.0.0: Major API simplification and consolidation.
  • pipes-3.2.0: ListT integration, Codensity proxy transformer, and ArrowChoice primitives.

[edit] 5 Upcoming libraries

  • pipes-bytestring: ByteString support. Source code is hosted at GitHub
  • pipes-text: Text support

[edit] 6 Videos

  • Pipes, by Oliver Charles. London Haskell user group, 18th September 2013.

[edit] 7 See also