Lines Matching full:be
22 in the specification of this API, there might be incompatibilities
30 (also known as the "tcpip_thread"). The raw API may only be used from
34 As such, the list of functions that may be called from
44 Additionaly, memory (de-)allocation functions may be
51 pbuf_free() may also be called from another thread or
53 be called from an ISR: otherwise, the HEAP is only
71 is the preferred way of writing applications that should be small in
74 Both APIs can be used simultaneously by different application
83 argument. Also, in order to be able to keep program specific state,
91 Specifies the program specific state that should be passed to all
94 that will be passed to the callbacks.
102 tcp_new() function. This PCB can then be either set to listen for new
103 incoming connections or be explicitly connected to another host.
114 can be specified as IP_ADDR_ANY in order to bind the connection to
124 tcp_accept() function will be called. The pcb will have to be bound
128 the one passed as an argument to the function will be
136 passed as an argument to tcp_listen() will not be deallocated.
147 usually be called from the accept callback. This allows lwIP to perform
148 housekeeping tasks, such as allowing further incoming connections to be
150 ATTENTION: the PCB passed in must be the listening pcb, not the pcb passed
157 Specified the callback function that should be called when a new
169 the connection to be properly setup. Instead, it will call the
171 when the connection is established. If the connection could not be
175 will be called.
186 host, the application will be notified with a call to a specified
193 the data is passed as the len parameter. The apiflags can be one or more of:
194 - TCP_WRITE_FLAG_COPY: indicates whether the new memory should be allocated
195 for the data to be copied into. If this flag is not given, no new memory
196 should be allocated and the data should only be referenced by pointer. This
207 be retrieved with the tcp_sndbuf() function.
218 Specifies the callback function that should be called when data has
236 Sets the callback function that will be called when new data
237 arrives. The callback function will be passed a NULL pbuf to
245 Must be called when the application has received the data. The len
253 specified callback function. This can be used either as a watchdog
265 be called to poll the application. The interval is specified in
268 be polled every 5 seconds.
296 function to be called is set using the tcp_err() function.
309 to be called before any other TCP function is called. When the system
311 must be called with regular intervals. The tcp_fasttmr() should be
313 tcp_slowtmr() should be called every TCP_SLOW_INTERVAL milliseconds.
323 Creates a new UDP pcb which can be used for UDP communication. The
335 can be IP_ADDR_ANY to indicate that it should listen to any local IP
360 Specifies a callback function that should be called when a UDP
367 cannot be given because it depends on the build configuration (lwipopts.h)
383 to be called for easy configuration changes.
405 Doesn't do much, it should be called to handle future changes.
425 or fill them with sane numbers otherwise. The state pointer may be NULL.
449 When the netif is fully configured this function must be called.
470 Other significant improvements can be made by supplying
498 when the packets have been enqueued for sending, data must be kept stable
502 must *not* be reused by the application unless their ref-count is 1.
504 For no-copy pbufs (PBUF_ROM/PBUF_REF), data must be kept unchanged, too,
508 Also, data passed to tcp_write without the copy-flag must not be changed!
510 Therefore, be careful which type of PBUF you use and if you copy TCP data