Lines Matching refs:an
47 This can be resolved using threads or with an event-driven model.
53 programming in an asynchronous event-driven paradigm.
64 define an abstract "object" that is used by other parts of
68 an interface for managing asynchronous transactions within
83 an "object", but rather perform a specific task. Examples
104 libinetutil. The event handler is essentially an object-oriented
118 registered -- this is the classic event-driven model. (As an aside,
119 note that programming in an event-driven model means that callbacks
125 forth), an object-oriented abstraction to timers called a "timer
165 associated with DUID value rather than with just an interface.
181 As an example, consider the process of extending a lease: the agent
182 must send a REQUEST packet and wait for an ACK or NAK packet in
184 event handler that waits for an ACK or NAK packet to arrive on the
188 back its context). This could be handled through an ad-hoc mapping of
190 the event handler's register function (iu_register_event()) take in an
209 DISCOVER, collecting OFFERs, selecting an OFFER, sending a REQUEST,
210 and receiving an ACK, assuming everything goes well. Note however
215 on another state machine), eventually checks to see if an acceptable
219 if while the agent is waiting for an OFFER on a given state machine,
220 an IPC event comes in requesting that the leases be RELEASED, the
221 agent knows to send back an error since the state machine must be in
226 packet and waiting for an ACK or NAK, which might never come. If,
235 In short, an `async_action' represents a pending transaction (aka
249 When the agent realizes it must perform an asynchronous transaction,
264 For instance, a user initiates an asynchronous START transaction when
265 he performs an `ifconfig hme0 dhcp start', but the agent will
272 represents the IPC-related pieces of an asynchronous transaction that
281 events. When the user specifies a timeout value as an argument to
282 ifconfig, he is specifying an `ipc_action' timeout; in other words,
288 one for the `async_action' object: when an IPC request comes in for an
321 retransmission mechanism. See request.c for an example of this in
326 once. The caller registers an event handler on the file descriptor,
337 to allow unicast DHCP traffic to be received on an interface during
344 The notion of time is an exceptionally subtle area. You will notice
368 general to represent an absolute time since the epoch. For instance,
375 must be obtained (such as when caching an ACK packet at system
455 DHCP command START is considered over when an ACK is received and the