2 .TH selpk 3 "23 May 1999" "Straylight/Edgeware" "mLib utilities library"
4 selpk \- packet-buffering input selector
12 .B "#include <mLib/selpk.h>"
14 .BI "void selpk_enable(selpk *" pk );
15 .BI "void selpk_disable(selpk *" pk );
16 .BI "void selpk_want(selpk *" pk ", size_t " sz );
17 .BI "void selpk_init(selpk *" pk ", sel_state *" s ", int " fd ,
18 .BI " pkbuf_func *" func ", void *" p );
19 .BI "void selpk_destroy(selpk *" b );
24 subsystem is a selector which integrates with the
26 system for I/O multiplexing. It reads packets from a file descriptor
27 and passes them to a caller-defined function. It uses the packet buffer
30 to do its work: you should read about it in order to understand exactly
31 how the packet buffer decides how much data is in each packet and the
32 exact rules about what your packet handling function should and
35 The data for a packet selector is stored in an object of type
37 This object must be allocated by the caller, and initialized using the
39 function. This requires a fair few arguments:
47 Pointer to a multiplexor object (type
49 to which this selector should be attached. See
51 for more details about multiplexors, and how this whole system works.
54 The file descriptor of the stream the selector should read from.
56 .BI "pkbuf_func *" func
59 function. It is given a pointer to each packet read from the file (or
60 null to indicate end-of-file) and an arbitrary pointer (the
69 A pointer argument passed to
71 for each packet read from the file. Apart from this, the pointer is not
76 selector is immediately active. Subsequent calls to
78 on the same multiplexor will cause any packets read from the file to be
79 passed to your handling function. This function can at any time call
81 to stop itself from being called any more. The selector is then
82 disengaged from the I/O multiplexor and won't do anything until
86 may well immediately start emitting complete packets of text which were
87 queued up from the last I/O operation: it doesn't necessarily wait for
92 The size of packets read by the buffer is set by calling
96 for more details about how packet buffering works.
98 When it's finished with, a packet selector must be destroyed by calling
106 Mark Wooding, <mdw@distorted.org.uk>