Google

Main Page   Class Hierarchy   Alphabetical List   Compound List   File List   Compound Members   File Members  

Pipe Class Reference

The Pipe uses system kernel buffering to hold data being passed either between two execution contexts within the same process, or between different processes. kernel buffering between processes and/or threads. More...

#include <file.h>

List of all members.

Public Methods

bool operator! ()
 Used to see if the pipe has any open entities.

int Recv (void *addr)
 Perform an object atomic transfer of data from a pipe. More...

int Send (void *addr)
 Perform an object atomic transfer of data to a pipe. More...

bool isValid (void)
 Verify this object is "valid". More...


Protected Methods

int getSize (void)
 Get the object size for atomic operations. More...

void endSender (void)
 Sender is often used for implementing a fork()'d message port between processes. More...

void endReceiver (void)
 Receiver is often used for implementing a fork()'d message port between processes. More...

 Pipe (int size = 512, int count = 1)
 Create a kernel pipe descriptor set using pipe(). More...

 ~Pipe ()
 Destroy the pipe and kernel descriptor resources.

 Pipe (const Pipe &orig)
 Create a pipe as a duplicate of an existing pipe. More...

Pipe& operator= (const Pipe &orig)
void Sender (void)
void Receiver (void)
int Read (void *buf, int len)
int Write (void *buf, int len)


Detailed Description

The Pipe uses system kernel buffering to hold data being passed either between two execution contexts within the same process, or between different processes. kernel buffering between processes and/or threads.

Unlike thread's "Buffer", Pipe uses system descriptors and kernel memory. Under Posix, the size of the pipe and associated kernel memory is always a fixed constant as defined by _PC_PIPE_BUF. The Common C++ "pipe" class primarily deals with "atomic" transfers of fixed sized objects through pipes. Pipes may pass data arbitrarily and can also be used through the "pipestream" class.

The "Pipe" class is not meant to be a true "public" class, but as a builder class for deriving other classes.

Author(s):
David Sugar <dyfet@ostel.com>


Constructor & Destructor Documentation

Pipe::Pipe ( int size = 512,
int count = 1 ) [protected]
 

Create a kernel pipe descriptor set using pipe().

On systems which allow the pipe kernel buffer to be defined, a size for aligned atomic transfers can be set, as well as the number of atomic objects the kernel will buffer. On Posix systems, these options are ignored.

Parameters:
objsize   of atomic objects to send.
count   of atomic objects to kernel buffer.

Pipe::~Pipe ( ) [protected]
 

Destroy the pipe and kernel descriptor resources.

Pipe::Pipe ( const Pipe & orig ) [protected]
 

Create a pipe as a duplicate of an existing pipe.

Parameters:
orig   pipe to duplicate.


Member Function Documentation

int Pipe::Read ( void * buf,
int len ) [inline, protected]
 

void Pipe::Receiver ( void ) [inline, protected]
 

int Pipe::Recv ( void * addr ) [inline]
 

Perform an object atomic transfer of data from a pipe.

Returns:
number of bytes actually read if successful.
Parameters:
addr   pointer to store read data.
len   number of bytes to read.

int Pipe::Send ( void * addr ) [inline]
 

Perform an object atomic transfer of data to a pipe.

Returns:
number of bytes written if successful.
Parameters:
addr   pointer to write data from.
len   number of butes to write.

void Pipe::Sender ( void ) [inline, protected]
 

int Pipe::Write ( void * buf,
int len ) [inline, protected]
 

void Pipe::endReceiver ( void ) [inline, protected]
 

Receiver is often used for implementing a fork()'d message port between processes.

By stopping the receiver, the current pipe can then only be used for sending, and the receiver is presumed to be in the other half of a fork()'d process.

See also:
endSender

void Pipe::endSender ( void ) [inline, protected]
 

Sender is often used for implementing a fork()'d message port between processes.

By stopping the sender, the current pipe can then only be used for receiving, and the sender is presumed to be in the other half of a fork()'d process.

See also:
endReceiver

int Pipe::getSize ( void ) [inline, protected]
 

Get the object size for atomic operations.

Returns:
size of atomic operations.

bool Pipe::isValid ( void )
 

Verify this object is "valid".

Returns:
true if valid.

bool Pipe::operator! ( void )
 

Used to see if the pipe has any open entities.

Pipe& Pipe::operator= ( const Pipe & orig ) [protected]
 


The documentation for this class was generated from the following file:
Generated at Fri Mar 23 10:47:56 2001 for CommonC++ by doxygen1.2.1 written by Dimitri van Heesch, © 1997-2000