Lines Matching refs:callback

7 * low-level "core" / "callback" or "raw" API.
61 having callback functions being called from within the TCP/IP
80 Program execution is driven by callbacks. Each callback is an ordinary
81 C function that is called from within the TCP/IP code. Every callback
84 the callback functions are called with a program specified argument
92   other callback functions. The "pcb" argument is the current TCP
147   usually be called from the accept callback. This allows lwIP to perform
151   into the accept callback!
157   Specified the callback function that should be called when a new
174   callback function of this pcb (registered with tcp_err, see below)
187 callback function.
218   Specifies the callback function that should be called when data has
220   host. The len argument passed to the callback function gives the
226 TCP data reception is callback based - an application specified
227 callback function is called when new data arrives. When the
236   Sets the callback function that will be called when new data
237   arrives. The callback function will be passed a NULL pbuf to
239   there are no errors and the callback function is to return
253 specified callback function. This can be used either as a watchdog
264   Specifies the polling interval and the callback function that should
278   callback or the polling functionality. If the close succeeds, the
294 alerted of this event by the err callback. Errors that might abort a
295 connection are when there is a shortage of memory. The callback
301   The error callback function does not get the pcb passed to it as a
360   Specifies a callback function that should be called when a UDP