Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

iohandler(3i) [debian man page]

IOHandler(3I)						    InterViews Reference Manual 					     IOHandler(3I)

NAME
IOHandler - read input, write output, or handle an I/O exception or timeout SYNOPSIS
#include <Dispatch/iohandler.h> DESCRIPTION
An iohandler reads data from a file descriptor, writes data to a file descriptor, handles an I/O exception on a file descriptor, or handles a timer's expiration. Once the user has requested the dispatcher to attach an iohandler to a file descriptor or a timer, the dispatcher will automatically notify the iohandler when the file descriptor's I/O condition changes or the timer expires. For convenience, the user can use a derived generic class (see IOCallback(3I)) to make the iohandler do nothing more than call an arbitrary object's member function. PUBLIC OPERATIONS
virtual int inputReady(int fd) virtual int outputReady(int fd) virtual int exceptionRaised(int fd) The dispatcher will call one of these functions to notify an iohandler that it can read data from a file descriptor, write data to a file descriptor, or handle an I/O exception on a file descriptor. The iohandler should perform the appropriate action and tell the dispatcher what to do next. A negative return value means that the iohandler encountered an error or it doesn't want to read or write anything more. The dispatcher will unlink the iohandler from its file descriptor automatically. A positive return value means that the iohandler didn't read or write everything that it could have. The dispatcher will call the iohandler again in round robin fashion WITHOUT checking select, which means that the iohandler will be called again as soon as the rest of the iohandlers have performed their actions. A zero return value means that the iohandler finished reading or writing everything it was able to. The dispatcher must check the descriptor's status with the select call before it can call the iohandler again. virtual void timerExpired(long sec, long usec) The dispatcher will call this function to notify an iohandler that a timer has expired. For informational purposes, the parameters give the current time in seconds and microseconds since midnight January 1, 1970. If the iohandler wants to reset the timer, it must tell the dispatcher to start another timer. SEE ALSO
Dispatcher(3I), IOCallback(3I) InterViews 9 January 1991 IOHandler(3I)

Check Out this Related Man Page

Xserver(1)						      General Commands Manual							Xserver(1)

NAME
X - X Window System display server dispatcher SYNOPSIS
X [ option ...] DESCRIPTION
: Hewlett-Packard supports two X servers on HP-UX platforms, the Xhp X server which supports HP VISUALIZE graphics devices and the Xf86 X server which supports all other graphics devices. These X servers are delivered as /usr/bin/X11/Xhp and /usr/bin/X11/Xf86. The X dispatcher determines which X server to launch based on the available graphics devices. The control file /etc/X11/Xstart can provide additional guidance to the X dispatcher. The control file allows the user to specify which X server to start for given display connection numbers. The only X servers supported by the X dispatcher are Xhp, Xf86 and Xvfb. If no Xstart file exists, the dispatcher loads the appropriate X server for the graphics device in the system. HP-UX does not deliver the /etc/X11/Xstart file. This file can be created by using the SAM/SMH utility. OPTIONS
If the X dispatcher is invoked with no arguments, the display connection is assumed to be :0. The X dispatcher checks for display connec- tion options and, if found, uses that display connection number when it checks the Xstart file. All other options are passed on to the X server when it is started and it is the X server's responsibility to validate these options. Not all options may be supported on both X servers; refer to Xhp(1) and Xf86(1) to verify supported options for each X server. RETURN VALUE
None Xstart EXAMPLES The control file syntax is the X server to start followed by the display connection number. Valid entries take the form of: Xhp :0 Start the Xhp X server on display connection 0 Xf86 :10 Start the Xf86 X server on display 10 /usr/bin/X11/Xhp :5 Start the Xhp X server on display connection 5 /usr/bin/X11/Xvfb :7 Start the X Virtual Framebuffer server on display connection 7 FILES
/etc/X11/Xstart Dispatcher control file. /var/X11/Xserver/logs/Xstartup.N.log X dispatcher log file for display N. SEE ALSO
X(1), Xhp(1), Xf86(1) STANDARDS CONFORMANCE
See the appropriate section in Xhp(1) or Xf86(1). Xserver(1)
Man Page