Editing Pipeline (software) (section)

==Other considerations==
The name "pipeline" comes from a rough analogy with physical plumbing in that a pipeline usually<ref>There are exceptions, such as "broken pipe" signals.</ref> allows information to flow in only one direction, like water often flows in a pipe.

Pipes and [[Filter (software)|filters]] can be viewed as a form of [[functional programming]], using byte streams as data objects. More specifically, they can be seen as a particular form of [[Monads in functional programming|monad]] for [[I/O]].<ref>[http://okmij.org/ftp/Computation/monadic-shell.html "Monadic I/O and UNIX shell programming"] {{Webarchive|url=https://web.archive.org/web/20201109030741/http://okmij.org/ftp/Computation/monadic-shell.html |date=2020-11-09 }}.</ref>

The concept of pipeline is also central to the [[Apache Cocoon|Cocoon]] web development [[Software framework|framework]] or to any [[XProc]] (the W3C Standards) implementations, where it allows a source stream to be modified before eventual display.

This pattern encourages the use of text streams as the input and output of programs. This reliance on text has to be accounted when creating [[GUI|graphic]] shells to text programs.