ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.html
(Generate patch)

Comparing libev/ev.html (file contents):
Revision 1.68 by root, Fri Dec 7 20:13:09 2007 UTC vs.
Revision 1.77 by root, Wed Dec 12 04:53:58 2007 UTC

… …
4<head> 4<head>
5 <title>libev</title> 5 <title>libev</title>
6 <meta name="description" content="Pod documentation for libev" /> 6 <meta name="description" content="Pod documentation for libev" />
7 <meta name="inputfile" content="&lt;standard input&gt;" /> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8 <meta name="outputfile" content="&lt;standard output&gt;" /> 8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Fri Dec 7 21:13:07 2007" /> 9 <meta name="created" content="Wed Dec 12 05:53:55 2007" />
10 <meta name="generator" content="Pod::Xhtml 1.57" /> 10 <meta name="generator" content="Pod::Xhtml 1.57" />
11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> 11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
12<body> 12<body>
13<div class="pod"> 13<div class="pod">
14<!-- INDEX START --> 14<!-- INDEX START -->
… …
27<ul><li><a href="#GENERIC_WATCHER_FUNCTIONS">GENERIC WATCHER FUNCTIONS</a></li> 27<ul><li><a href="#GENERIC_WATCHER_FUNCTIONS">GENERIC WATCHER FUNCTIONS</a></li>
28<li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li> 28<li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li>
29</ul> 29</ul>
30</li> 30</li>
31<li><a href="#WATCHER_TYPES">WATCHER TYPES</a> 31<li><a href="#WATCHER_TYPES">WATCHER TYPES</a>
32<ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable?</a></li> 32<ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable?</a>
33<ul><li><a href="#The_special_problem_of_disappearing_">The special problem of disappearing file descriptors</a></li>
34</ul>
35</li>
33<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally repeating timeouts</a></li> 36<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally repeating timeouts</a></li>
34<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron?</a></li> 37<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron?</a></li>
35<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled!</a></li> 38<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled!</a></li>
36<li><a href="#code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</a></li> 39<li><a href="#code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</a></li>
37<li><a href="#code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</a></li> 40<li><a href="#code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</a></li>
… …
185you actually want to know.</p> 188you actually want to know.</p>
186 </dd> 189 </dd>
187 <dt>int ev_version_major ()</dt> 190 <dt>int ev_version_major ()</dt>
188 <dt>int ev_version_minor ()</dt> 191 <dt>int ev_version_minor ()</dt>
189 <dd> 192 <dd>
190 <p>You can find out the major and minor version numbers of the library 193 <p>You can find out the major and minor ABI version numbers of the library
191you linked against by calling the functions <code>ev_version_major</code> and 194you linked against by calling the functions <code>ev_version_major</code> and
192<code>ev_version_minor</code>. If you want, you can compare against the global 195<code>ev_version_minor</code>. If you want, you can compare against the global
193symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the 196symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the
194version of the library your program was compiled against.</p> 197version of the library your program was compiled against.</p>
198 <p>These version numbers refer to the ABI version of the library, not the
199release version.</p>
195 <p>Usually, it's a good idea to terminate if the major versions mismatch, 200 <p>Usually, it's a good idea to terminate if the major versions mismatch,
196as this indicates an incompatible change. Minor versions are usually 201as this indicates an incompatible change. Minor versions are usually
197compatible to older versions, so a larger minor version alone is usually 202compatible to older versions, so a larger minor version alone is usually
198not a problem.</p> 203not a problem.</p>
199 <p>Example: Make sure we haven't accidentally been linked against the wrong 204 <p>Example: Make sure we haven't accidentally been linked against the wrong
200version.</p> 205version.</p>
201<pre> assert ((&quot;libev version mismatch&quot;, 206<pre> assert ((&quot;libev version mismatch&quot;,
… …
529one iteration of the loop. This is useful if you are waiting for some 534one iteration of the loop. This is useful if you are waiting for some
530external event in conjunction with something not expressible using other 535external event in conjunction with something not expressible using other
531libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is 536libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is
532usually a better approach for this kind of thing.</p> 537usually a better approach for this kind of thing.</p>
533 <p>Here are the gory details of what <code>ev_loop</code> does:</p> 538 <p>Here are the gory details of what <code>ev_loop</code> does:</p>
539<pre> - Before the first iteration, call any pending watchers.
534<pre> * If there are no active watchers (reference count is zero), return. 540 * If there are no active watchers (reference count is zero), return.
535 - Queue prepare watchers and then call all outstanding watchers. 541 - Queue all prepare watchers and then call all outstanding watchers.
536 - If we have been forked, recreate the kernel state. 542 - If we have been forked, recreate the kernel state.
537 - Update the kernel state with all outstanding changes. 543 - Update the kernel state with all outstanding changes.
538 - Update the &quot;event loop time&quot;. 544 - Update the &quot;event loop time&quot;.
539 - Calculate for how long to block. 545 - Calculate for how long to block.
540 - Block the process, waiting for any events. 546 - Block the process, waiting for any events.
… …
769 <dt>bool ev_is_pending (ev_TYPE *watcher)</dt> 775 <dt>bool ev_is_pending (ev_TYPE *watcher)</dt>
770 <dd> 776 <dd>
771 <p>Returns a true value iff the watcher is pending, (i.e. it has outstanding 777 <p>Returns a true value iff the watcher is pending, (i.e. it has outstanding
772events but its callback has not yet been invoked). As long as a watcher 778events but its callback has not yet been invoked). As long as a watcher
773is pending (but not active) you must not call an init function on it (but 779is pending (but not active) you must not call an init function on it (but
774<code>ev_TYPE_set</code> is safe) and you must make sure the watcher is available to 780<code>ev_TYPE_set</code> is safe), you must not change its priority, and you must
775libev (e.g. you cnanot <code>free ()</code> it).</p> 781make sure the watcher is available to libev (e.g. you cannot <code>free ()</code>
782it).</p>
776 </dd> 783 </dd>
777 <dt>callback ev_cb (ev_TYPE *watcher)</dt> 784 <dt>callback ev_cb (ev_TYPE *watcher)</dt>
778 <dd> 785 <dd>
779 <p>Returns the callback currently set on the watcher.</p> 786 <p>Returns the callback currently set on the watcher.</p>
780 </dd> 787 </dd>
… …
795invocation after new events have been received. This is useful, for 802invocation after new events have been received. This is useful, for
796example, to reduce latency after idling, or more often, to bind two 803example, to reduce latency after idling, or more often, to bind two
797watchers on the same event and make sure one is called first.</p> 804watchers on the same event and make sure one is called first.</p>
798 <p>If you need to suppress invocation when higher priority events are pending 805 <p>If you need to suppress invocation when higher priority events are pending
799you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p> 806you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p>
807 <p>You <i>must not</i> change the priority of a watcher as long as it is active or
808pending.</p>
800 <p>The default priority used by watchers when no priority has been set is 809 <p>The default priority used by watchers when no priority has been set is
801always <code>0</code>, which is supposed to not be too high and not be too low :).</p> 810always <code>0</code>, which is supposed to not be too high and not be too low :).</p>
802 <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is 811 <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is
803fine, as long as you do not mind that the priority value you query might 812fine, as long as you do not mind that the priority value you query might
804or might not have been adjusted to be within valid range.</p> 813or might not have been adjusted to be within valid range.</p>
814 </dd>
815 <dt>ev_invoke (loop, ev_TYPE *watcher, int revents)</dt>
816 <dd>
817 <p>Invoke the <code>watcher</code> with the given <code>loop</code> and <code>revents</code>. Neither
818<code>loop</code> nor <code>revents</code> need to be valid as long as the watcher callback
819can deal with that fact.</p>
820 </dd>
821 <dt>int ev_clear_pending (loop, ev_TYPE *watcher)</dt>
822 <dd>
823 <p>If the watcher is pending, this function returns clears its pending status
824and returns its <code>revents</code> bitset (as if its callback was invoked). If the
825watcher isn't pending it does nothing and returns <code>0</code>.</p>
805 </dd> 826 </dd>
806</dl> 827</dl>
807 828
808 829
809 830
… …
923<p>If you cannot run the fd in non-blocking mode (for example you should not 944<p>If you cannot run the fd in non-blocking mode (for example you should not
924play around with an Xlib connection), then you have to seperately re-test 945play around with an Xlib connection), then you have to seperately re-test
925whether a file descriptor is really ready with a known-to-be good interface 946whether a file descriptor is really ready with a known-to-be good interface
926such as poll (fortunately in our Xlib example, Xlib already does this on 947such as poll (fortunately in our Xlib example, Xlib already does this on
927its own, so its quite safe to use).</p> 948its own, so its quite safe to use).</p>
949
950</div>
951<h3 id="The_special_problem_of_disappearing_">The special problem of disappearing file descriptors</h3>
952<div id="The_special_problem_of_disappearing_-2">
953<p>Some backends (e.g kqueue, epoll) need to be told about closing a file
954descriptor (either by calling <code>close</code> explicitly or by any other means,
955such as <code>dup</code>). The reason is that you register interest in some file
956descriptor, but when it goes away, the operating system will silently drop
957this interest. If another file descriptor with the same number then is
958registered with libev, there is no efficient way to see that this is, in
959fact, a different file descriptor.</p>
960<p>To avoid having to explicitly tell libev about such cases, libev follows
961the following policy: Each time <code>ev_io_set</code> is being called, libev
962will assume that this is potentially a new file descriptor, otherwise
963it is assumed that the file descriptor stays the same. That means that
964you <i>have</i> to call <code>ev_io_set</code> (or <code>ev_io_init</code>) when you change the
965descriptor even if the file descriptor number itself did not change.</p>
966<p>This is how one would do it normally anyway, the important point is that
967the libev application should not optimise around libev but should leave
968optimisations to libev.</p>
969
970
971
972
928<dl> 973<dl>
929 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> 974 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt>
930 <dt>ev_io_set (ev_io *, int fd, int events)</dt> 975 <dt>ev_io_set (ev_io *, int fd, int events)</dt>
931 <dd> 976 <dd>
932 <p>Configures an <code>ev_io</code> watcher. The <code>fd</code> is the file descriptor to 977 <p>Configures an <code>ev_io</code> watcher. The <code>fd</code> is the file descriptor to
… …
1081but on wallclock time (absolute time). You can tell a periodic watcher 1126but on wallclock time (absolute time). You can tell a periodic watcher
1082to trigger &quot;at&quot; some specific point in time. For example, if you tell a 1127to trigger &quot;at&quot; some specific point in time. For example, if you tell a
1083periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now () 1128periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now ()
1084+ 10.</code>) and then reset your system clock to the last year, then it will 1129+ 10.</code>) and then reset your system clock to the last year, then it will
1085take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger 1130take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
1086roughly 10 seconds later and of course not if you reset your system time 1131roughly 10 seconds later).</p>
1087again).</p>
1088<p>They can also be used to implement vastly more complex timers, such as 1132<p>They can also be used to implement vastly more complex timers, such as
1089triggering an event on eahc midnight, local time.</p> 1133triggering an event on each midnight, local time or other, complicated,
1134rules.</p>
1090<p>As with timers, the callback is guarenteed to be invoked only when the 1135<p>As with timers, the callback is guarenteed to be invoked only when the
1091time (<code>at</code>) has been passed, but if multiple periodic timers become ready 1136time (<code>at</code>) has been passed, but if multiple periodic timers become ready
1092during the same loop iteration then order of execution is undefined.</p> 1137during the same loop iteration then order of execution is undefined.</p>
1093<dl> 1138<dl>
1094 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt> 1139 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt>
… …
1096 <dd> 1141 <dd>
1097 <p>Lots of arguments, lets sort it out... There are basically three modes of 1142 <p>Lots of arguments, lets sort it out... There are basically three modes of
1098operation, and we will explain them from simplest to complex:</p> 1143operation, and we will explain them from simplest to complex:</p>
1099 <p> 1144 <p>
1100 <dl> 1145 <dl>
1101 <dt>* absolute timer (interval = reschedule_cb = 0)</dt> 1146 <dt>* absolute timer (at = time, interval = reschedule_cb = 0)</dt>
1102 <dd> 1147 <dd>
1103 <p>In this configuration the watcher triggers an event at the wallclock time 1148 <p>In this configuration the watcher triggers an event at the wallclock time
1104<code>at</code> and doesn't repeat. It will not adjust when a time jump occurs, 1149<code>at</code> and doesn't repeat. It will not adjust when a time jump occurs,
1105that is, if it is to be run at January 1st 2011 then it will run when the 1150that is, if it is to be run at January 1st 2011 then it will run when the
1106system time reaches or surpasses this time.</p> 1151system time reaches or surpasses this time.</p>
1107 </dd> 1152 </dd>
1108 <dt>* non-repeating interval timer (interval &gt; 0, reschedule_cb = 0)</dt> 1153 <dt>* non-repeating interval timer (at = offset, interval &gt; 0, reschedule_cb = 0)</dt>
1109 <dd> 1154 <dd>
1110 <p>In this mode the watcher will always be scheduled to time out at the next 1155 <p>In this mode the watcher will always be scheduled to time out at the next
1111<code>at + N * interval</code> time (for some integer N) and then repeat, regardless 1156<code>at + N * interval</code> time (for some integer N, which can also be negative)
1112of any time jumps.</p> 1157and then repeat, regardless of any time jumps.</p>
1113 <p>This can be used to create timers that do not drift with respect to system 1158 <p>This can be used to create timers that do not drift with respect to system
1114time:</p> 1159time:</p>
1115<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0); 1160<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0);
1116 1161
1117</pre> 1162</pre>
… …
1120full hour (UTC), or more correctly, when the system time is evenly divisible 1165full hour (UTC), or more correctly, when the system time is evenly divisible
1121by 3600.</p> 1166by 3600.</p>
1122 <p>Another way to think about it (for the mathematically inclined) is that 1167 <p>Another way to think about it (for the mathematically inclined) is that
1123<code>ev_periodic</code> will try to run the callback in this mode at the next possible 1168<code>ev_periodic</code> will try to run the callback in this mode at the next possible
1124time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> 1169time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p>
1170 <p>For numerical stability it is preferable that the <code>at</code> value is near
1171<code>ev_now ()</code> (the current time), but there is no range requirement for
1172this value.</p>
1125 </dd> 1173 </dd>
1126 <dt>* manual reschedule mode (reschedule_cb = callback)</dt> 1174 <dt>* manual reschedule mode (at and interval ignored, reschedule_cb = callback)</dt>
1127 <dd> 1175 <dd>
1128 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being 1176 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being
1129ignored. Instead, each time the periodic watcher gets scheduled, the 1177ignored. Instead, each time the periodic watcher gets scheduled, the
1130reschedule callback will be called with the watcher as first, and the 1178reschedule callback will be called with the watcher as first, and the
1131current time as second argument.</p> 1179current time as second argument.</p>
1132 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher, 1180 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher,
1133ever, or make any event loop modifications</i>. If you need to stop it, 1181ever, or make any event loop modifications</i>. If you need to stop it,
1134return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by 1182return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by
1135starting a prepare watcher).</p> 1183starting an <code>ev_prepare</code> watcher, which is legal).</p>
1136 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 1184 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
1137ev_tstamp now)</code>, e.g.:</p> 1185ev_tstamp now)</code>, e.g.:</p>
1138<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) 1186<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
1139 { 1187 {
1140 return now + 60.; 1188 return now + 60.;
… …
1160 <dd> 1208 <dd>
1161 <p>Simply stops and restarts the periodic watcher again. This is only useful 1209 <p>Simply stops and restarts the periodic watcher again. This is only useful
1162when you changed some parameters or the reschedule callback would return 1210when you changed some parameters or the reschedule callback would return
1163a different time than the last time it was called (e.g. in a crond like 1211a different time than the last time it was called (e.g. in a crond like
1164program when the crontabs have changed).</p> 1212program when the crontabs have changed).</p>
1213 </dd>
1214 <dt>ev_tstamp offset [read-write]</dt>
1215 <dd>
1216 <p>When repeating, this contains the offset value, otherwise this is the
1217absolute point in time (the <code>at</code> value passed to <code>ev_periodic_set</code>).</p>
1218 <p>Can be modified any time, but changes only take effect when the periodic
1219timer fires or <code>ev_periodic_again</code> is being called.</p>
1165 </dd> 1220 </dd>
1166 <dt>ev_tstamp interval [read-write]</dt> 1221 <dt>ev_tstamp interval [read-write]</dt>
1167 <dd> 1222 <dd>
1168 <p>The current interval value. Can be modified any time, but changes only 1223 <p>The current interval value. Can be modified any time, but changes only
1169take effect when the periodic timer fires or <code>ev_periodic_again</code> is being 1224take effect when the periodic timer fires or <code>ev_periodic_again</code> is being
… …
1468are ready to run (it's actually more complicated: it only runs coroutines 1523are ready to run (it's actually more complicated: it only runs coroutines
1469with priority higher than or equal to the event loop and one coroutine 1524with priority higher than or equal to the event loop and one coroutine
1470of lower priority, but only once, using idle watchers to keep the event 1525of lower priority, but only once, using idle watchers to keep the event
1471loop from blocking if lower-priority coroutines are active, thus mapping 1526loop from blocking if lower-priority coroutines are active, thus mapping
1472low-priority coroutines to idle/background tasks).</p> 1527low-priority coroutines to idle/background tasks).</p>
1528<p>It is recommended to give <code>ev_check</code> watchers highest (<code>EV_MAXPRI</code>)
1529priority, to ensure that they are being run before any other watchers
1530after the poll. Also, <code>ev_check</code> watchers (and <code>ev_prepare</code> watchers,
1531too) should not activate (&quot;feed&quot;) events into libev. While libev fully
1532supports this, they will be called before other <code>ev_check</code> watchers did
1533their job. As <code>ev_check</code> watchers are often used to embed other event
1534loops those other event loops might be in an unusable state until their
1535<code>ev_check</code> watcher ran (always remind yourself to coexist peacefully with
1536others).</p>
1473<dl> 1537<dl>
1474 <dt>ev_prepare_init (ev_prepare *, callback)</dt> 1538 <dt>ev_prepare_init (ev_prepare *, callback)</dt>
1475 <dt>ev_check_init (ev_check *, callback)</dt> 1539 <dt>ev_check_init (ev_check *, callback)</dt>
1476 <dd> 1540 <dd>
1477 <p>Initialises and configures the prepare or check watcher - they have no 1541 <p>Initialises and configures the prepare or check watcher - they have no
1478parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> 1542parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code>
1479macros, but using them is utterly, utterly and completely pointless.</p> 1543macros, but using them is utterly, utterly and completely pointless.</p>
1480 </dd> 1544 </dd>
1481</dl> 1545</dl>
1482<p>Example: To include a library such as adns, you would add IO watchers 1546<p>There are a number of principal ways to embed other event loops or modules
1483and a timeout watcher in a prepare handler, as required by libadns, and 1547into libev. Here are some ideas on how to include libadns into libev
1548(there is a Perl module named <code>EV::ADNS</code> that does this, which you could
1549use for an actually working example. Another Perl module named <code>EV::Glib</code>
1550embeds a Glib main context into libev, and finally, <code>Glib::EV</code> embeds EV
1551into the Glib event loop).</p>
1552<p>Method 1: Add IO watchers and a timeout watcher in a prepare handler,
1484in a check watcher, destroy them and call into libadns. What follows is 1553and in a check watcher, destroy them and call into libadns. What follows
1485pseudo-code only of course:</p> 1554is pseudo-code only of course. This requires you to either use a low
1555priority for the check watcher or use <code>ev_clear_pending</code> explicitly, as
1556the callbacks for the IO/timeout watchers might not have been called yet.</p>
1486<pre> static ev_io iow [nfd]; 1557<pre> static ev_io iow [nfd];
1487 static ev_timer tw; 1558 static ev_timer tw;
1488 1559
1489 static void 1560 static void
1490 io_cb (ev_loop *loop, ev_io *w, int revents) 1561 io_cb (ev_loop *loop, ev_io *w, int revents)
1491 { 1562 {
1492 // set the relevant poll flags
1493 // could also call adns_processreadable etc. here
1494 struct pollfd *fd = (struct pollfd *)w-&gt;data;
1495 if (revents &amp; EV_READ ) fd-&gt;revents |= fd-&gt;events &amp; POLLIN;
1496 if (revents &amp; EV_WRITE) fd-&gt;revents |= fd-&gt;events &amp; POLLOUT;
1497 } 1563 }
1498 1564
1499 // create io watchers for each fd and a timer before blocking 1565 // create io watchers for each fd and a timer before blocking
1500 static void 1566 static void
1501 adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) 1567 adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
… …
1507 1573
1508 /* the callback is illegal, but won't be called as we stop during check */ 1574 /* the callback is illegal, but won't be called as we stop during check */
1509 ev_timer_init (&amp;tw, 0, timeout * 1e-3); 1575 ev_timer_init (&amp;tw, 0, timeout * 1e-3);
1510 ev_timer_start (loop, &amp;tw); 1576 ev_timer_start (loop, &amp;tw);
1511 1577
1512 // create on ev_io per pollfd 1578 // create one ev_io per pollfd
1513 for (int i = 0; i &lt; nfd; ++i) 1579 for (int i = 0; i &lt; nfd; ++i)
1514 { 1580 {
1515 ev_io_init (iow + i, io_cb, fds [i].fd, 1581 ev_io_init (iow + i, io_cb, fds [i].fd,
1516 ((fds [i].events &amp; POLLIN ? EV_READ : 0) 1582 ((fds [i].events &amp; POLLIN ? EV_READ : 0)
1517 | (fds [i].events &amp; POLLOUT ? EV_WRITE : 0))); 1583 | (fds [i].events &amp; POLLOUT ? EV_WRITE : 0)));
1518 1584
1519 fds [i].revents = 0; 1585 fds [i].revents = 0;
1520 iow [i].data = fds + i;
1521 ev_io_start (loop, iow + i); 1586 ev_io_start (loop, iow + i);
1522 } 1587 }
1523 } 1588 }
1524 1589
1525 // stop all watchers after blocking 1590 // stop all watchers after blocking
… …
1527 adns_check_cb (ev_loop *loop, ev_check *w, int revents) 1592 adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1528 { 1593 {
1529 ev_timer_stop (loop, &amp;tw); 1594 ev_timer_stop (loop, &amp;tw);
1530 1595
1531 for (int i = 0; i &lt; nfd; ++i) 1596 for (int i = 0; i &lt; nfd; ++i)
1597 {
1598 // set the relevant poll flags
1599 // could also call adns_processreadable etc. here
1600 struct pollfd *fd = fds + i;
1601 int revents = ev_clear_pending (iow + i);
1602 if (revents &amp; EV_READ ) fd-&gt;revents |= fd-&gt;events &amp; POLLIN;
1603 if (revents &amp; EV_WRITE) fd-&gt;revents |= fd-&gt;events &amp; POLLOUT;
1604
1605 // now stop the watcher
1532 ev_io_stop (loop, iow + i); 1606 ev_io_stop (loop, iow + i);
1607 }
1533 1608
1534 adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); 1609 adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1610 }
1611
1612</pre>
1613<p>Method 2: This would be just like method 1, but you run <code>adns_afterpoll</code>
1614in the prepare watcher and would dispose of the check watcher.</p>
1615<p>Method 3: If the module to be embedded supports explicit event
1616notification (adns does), you can also make use of the actual watcher
1617callbacks, and only destroy/create the watchers in the prepare watcher.</p>
1618<pre> static void
1619 timer_cb (EV_P_ ev_timer *w, int revents)
1620 {
1621 adns_state ads = (adns_state)w-&gt;data;
1622 update_now (EV_A);
1623
1624 adns_processtimeouts (ads, &amp;tv_now);
1625 }
1626
1627 static void
1628 io_cb (EV_P_ ev_io *w, int revents)
1629 {
1630 adns_state ads = (adns_state)w-&gt;data;
1631 update_now (EV_A);
1632
1633 if (revents &amp; EV_READ ) adns_processreadable (ads, w-&gt;fd, &amp;tv_now);
1634 if (revents &amp; EV_WRITE) adns_processwriteable (ads, w-&gt;fd, &amp;tv_now);
1635 }
1636
1637 // do not ever call adns_afterpoll
1638
1639</pre>
1640<p>Method 4: Do not use a prepare or check watcher because the module you
1641want to embed is too inflexible to support it. Instead, youc na override
1642their poll function. The drawback with this solution is that the main
1643loop is now no longer controllable by EV. The <code>Glib::EV</code> module does
1644this.</p>
1645<pre> static gint
1646 event_poll_func (GPollFD *fds, guint nfds, gint timeout)
1647 {
1648 int got_events = 0;
1649
1650 for (n = 0; n &lt; nfds; ++n)
1651 // create/start io watcher that sets the relevant bits in fds[n] and increment got_events
1652
1653 if (timeout &gt;= 0)
1654 // create/start timer
1655
1656 // poll
1657 ev_loop (EV_A_ 0);
1658
1659 // stop timer again
1660 if (timeout &gt;= 0)
1661 ev_timer_stop (EV_A_ &amp;to);
1662
1663 // stop io watchers again - their callbacks should have set
1664 for (n = 0; n &lt; nfds; ++n)
1665 ev_io_stop (EV_A_ iow [n]);
1666
1667 return got_events;
1535 } 1668 }
1536 1669
1537 1670
1538 1671
1539 1672
… …
1740</pre> 1873</pre>
1741<p>This automatically includes <cite>ev.h</cite> and puts all of its definitions (many 1874<p>This automatically includes <cite>ev.h</cite> and puts all of its definitions (many
1742of them macros) into the global namespace. All C++ specific things are 1875of them macros) into the global namespace. All C++ specific things are
1743put into the <code>ev</code> namespace. It should support all the same embedding 1876put into the <code>ev</code> namespace. It should support all the same embedding
1744options as <cite>ev.h</cite>, most notably <code>EV_MULTIPLICITY</code>.</p> 1877options as <cite>ev.h</cite>, most notably <code>EV_MULTIPLICITY</code>.</p>
1745<p>Care has been taken to keep the overhead low. The only data member added 1878<p>Care has been taken to keep the overhead low. The only data member the C++
1746to the C-style watchers is the event loop the watcher is associated with 1879classes add (compared to plain C-style watchers) is the event loop pointer
1747(or no additional members at all if you disable <code>EV_MULTIPLICITY</code> when 1880that the watcher is associated with (or no additional members at all if
1748embedding libev).</p> 1881you disable <code>EV_MULTIPLICITY</code> when embedding libev).</p>
1749<p>Currently, functions and static and non-static member functions can be 1882<p>Currently, functions, and static and non-static member functions can be
1750used as callbacks. Other types should be easy to add as long as they only 1883used as callbacks. Other types should be easy to add as long as they only
1751need one additional pointer for context. If you need support for other 1884need one additional pointer for context. If you need support for other
1752types of functors please contact the author (preferably after implementing 1885types of functors please contact the author (preferably after implementing
1753it).</p> 1886it).</p>
1754<p>Here is a list of things available in the <code>ev</code> namespace:</p> 1887<p>Here is a list of things available in the <code>ev</code> namespace:</p>
… …
1806 ev::io iow; 1939 ev::io iow;
1807 iow.set &lt;myclass, &amp;myclass::io_cb&gt; (&amp;obj); 1940 iow.set &lt;myclass, &amp;myclass::io_cb&gt; (&amp;obj);
1808 1941
1809</pre> 1942</pre>
1810 </dd> 1943 </dd>
1811 <dt>w-&gt;set (void (*function)(watcher &amp;w, int), void *data = 0)</dt> 1944 <dt>w-&gt;set&lt;function&gt; (void *data = 0)</dt>
1812 <dd> 1945 <dd>
1813 <p>Also sets a callback, but uses a static method or plain function as 1946 <p>Also sets a callback, but uses a static method or plain function as
1814callback. The optional <code>data</code> argument will be stored in the watcher's 1947callback. The optional <code>data</code> argument will be stored in the watcher's
1815<code>data</code> member and is free for you to use.</p> 1948<code>data</code> member and is free for you to use.</p>
1949 <p>The prototype of the <code>function</code> must be <code>void (*)(ev::TYPE &amp;w, int)</code>.</p>
1816 <p>See the method-<code>set</code> above for more details.</p> 1950 <p>See the method-<code>set</code> above for more details.</p>
1951 <p>Example:</p>
1952<pre> static void io_cb (ev::io &amp;w, int revents) { }
1953 iow.set &lt;io_cb&gt; ();
1954
1955</pre>
1817 </dd> 1956 </dd>
1818 <dt>w-&gt;set (struct ev_loop *)</dt> 1957 <dt>w-&gt;set (struct ev_loop *)</dt>
1819 <dd> 1958 <dd>
1820 <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only 1959 <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only
1821do this when the watcher is inactive (and not pending either).</p> 1960do this when the watcher is inactive (and not pending either).</p>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines