Lines Matching full:by
13 receive. This API is also used by the core stack for interaction between
20 paradigm. Since the TCP/IP stack is event based by nature, the TCP/IP
56 since they are protected by SYS_LIGHTWEIGHT_PROT and/or
69 protected by semaphores).
75 better with the TCP/IP code. Program execution is event based by
89 All APIs can be used simultaneously by different application
104 Program execution is driven by callbacks functions, which are then
105 invoked by the lwIP core when activity related to that application
171 in the listen queue to the value specified by the backlog argument.
205 TCP data is sent by enqueueing the data with a call to
213 Enqueues the data pointed to by the argument dataptr. The length of
217 should be allocated and the data should only be referenced by pointer. This
219 ACKed by the remote host
221 the PSH flag is set in the last segment created by this call to tcp_write.
233 data has been successfully received by the other host and try again.
240 successfully been received (i.e., acknowledged) by the remote
242 amount bytes that was acknowledged by the last acknowledgment.
273 received), lwIP will repeatedly poll the application by calling a
298 should wait and try again either by using the acknowledgment
302 The pcb is deallocated by the TCP code after a call to tcp_close().
306 Aborts the connection by sending a RST (reset) segment to the remote
315 alerted of this event by the err callback. Errors that might abort a
456 Other significant improvements can be made by supplying
477 Note that speed performance isn't influenced much by simply setting
490 must *not* be reused by the application unless their ref-count is 1.