Lines Matching full:with

11 with peers running a similarly light-weight stack. The code size is on
29 With the success of the Internet, the TCP/IP protocol suite has become
35 with full TCP/IP support will be first-class network citizens, thus
36 being able to fully communicate with other hosts in the network.
42 impossible to fit the full TCP/IP stack into systems with a few tens
52 embedded device always will communicate with a full-scale TCP/IP
56 essential, however, if the embedded device is to communicate with
69 transfer e-mail. The uIP is mostly concerned with the TCP and IP
95 that deal with the host to host communication and those that deal with
101 the first kind may not be able to communicate with other TCP/IP
135 retransmissions when dealing with a timer event, the network device
179 scarce resource. With only a few kilobytes of RAM available for the
225 while at the same time running a web server with highly dynamic web
228 with as little as 200 bytes of RAM, but such a configuration will
236 application program interacts with the TCP/IP stack. The most commonly
265 function; it is up to the application to deal with mapping different
276 retransmission without notifying the application. With this approach,
287 retransmitted, it calls the application with a flag set indicating
307 conjunction with each other (i.e., new data can arrive at the same
365 retransmitted, the application function is called with the
419 listening with the uip_listen() function. When a connection request
481 is initialized with the function called example1_init() and the uIP
502 the remote end has sent it data, it responds with an "ok". If the
506 for an application to deal with all types of events such as
517 to it with a single "ok". The big difference is that this application
680 is restarted with uip_restart().
687 be used as a web server with static pages. The implementation follows.
750 act on acknowledged data, send new data, deal with connection
788 The function starts with dealing with any error conditions that might
792 deal with the event.
799 out, the senddata() function is called to deal with the outgoing data.
889 " message with the connection. This message will later be sent out by
912 calls uip_send() with the appropriate arguments if data is to be sent,
982 of incoming echo requests and rewriting the ICMP header with the
1038 as a sample of the RTT. The sample is used together with Van
1054 retransmitted, it calls the application with a flag set indicating
1070 between hosts with wildly varying memory dimensions. In each TCP
1118 with the checksum calculation. Because high-end systems usually have
1125 data between the TCP/IP stack and the application program. With an
1149 segment will interact poorly with the delayed acknowledgment
1158 500 ms. With a segment size of 1000 bytes, a round-trip time of 40 ms
1160 throughput will be 4166 bytes per second. With the delayed acknowledgment