STREAMS

<p>In <a href="/facts/Computer_network/3w5RM99p">computer networking</a>, STREAMS is the native framework in <a href="/facts/UNIX_System_V/Epm6GEY4">Unix System V</a> for implementing <a href="/facts/Character_device/t8ISnXft">character device</a> drivers, network protocols, and <a href="/facts/Inter-process_communication/cIQYyT6y">inter-process communication</a>. In this framework, a stream is a chain of <a href="/facts/Coroutine/hGCtXsAQ">coroutines</a> that <a href="/facts/Message_passing/RYf3hD3J">pass messages</a> between a program and a device driver (or between a pair of programs). STREAMS originated in Version 8 <a href="/facts/Research_Unix/5oWmUdwo">Research Unix</a>, as Streams (not capitalized).
</p><p>STREAMS's design is a modular architecture for implementing full-duplex <a href="/facts/Input%2foutput/WQTE8Jas">I/O</a> between kernel and device drivers. Its most frequent uses have been in developing terminal I/O (<a href="/facts/Line_discipline/0vqvgF4o">line discipline</a>) and networking subsystems. In System V Release 4, the entire terminal interface was reimplemented using STREAMS. An important concept in STREAMS is the ability to push drivers –  custom code modules which can modify the functionality of a network interface or other device –  together to form a stack. Several of these drivers can be chained together in order.
</p>

STREAMS open-in-new

STREAMS