Lines Matching full:are

55 are very rarely used in such situations. Many of those mechanisms are
71 application". Lower layer protocols are often implemented in hardware
72 or firmware and will be referred to as "the network device" that are
77 segment is sent in its own IP packet. The IP packets are sent out on
83 packets by the router. If possible, the size of the TCP segments are
107 are implemented. However, in order to reduce code size, we have
111 connections. Since there are only very few applications that make use
130 Periodic timeouts are used to drive TCP mechanisms that depend on
143 implementations are given as part of the uIP distribution.
198 Ethernet controllers have on-chip buffers that are large enough to
199 contain at least 4 maximum sized Ethernet frames. Devices that are
202 buffers are full, the incoming packet is dropped. This will cause
203 performance degradation, but only when multiple connections are
211 packet buffer that are not used for headers as a temporary storage
213 as well as the length of the data to the stack. The TCP/IP headers are
221 applications of the particular device in which the implementations are
305 events. The functions are implemented as C macros that will evaluate
358 Retransmissions are driven by the periodic TCP timer. Every time the
395 There are two fatal errors that can happen to a connection, either
436 connection. If there are no free connection slots, the function
442 Two examples of usage are shown below. The first example shows how to
444 connection. If there are not enough TCP connection slots to allow a
457 address. No error checks are made in this example.
686 send. If the files are properly formatted, this simple application can
751 establishment or closure events and handle errors. The functions are
789 have happened by checking if uip_aborted() or uip_timedout() are
877 and therefore the aborted(), timedout() and closed() functions are
922 The protocols in the TCP/IP protocol suite are designed in a layered
924 interactions between the protocol layers are strictly defined. While
927 implementations are tightly coupled in order to save code space.
934 When incoming packets are processed by uIP, the IP layer is the first
938 checksum. Since there are no IP options that are strictly required and
939 because they are very uncommon, any IP options in received packets are
956 reassembly of more than one packet. Since fragmented packets are
964 network. Such packets are addressed to special broadcast and multicast
980 only implement ICMP echo messages. Replies to echo messages are
988 strictly required for interoperability; they are performance
994 events. Incoming packets are parsed by TCP and if the packet contains
1005 and incoming connection requests are checked against the list of
1012 data. Multiple data segments are sent in succession without waiting
1045 Retransmissions are driven by the periodic TCP timer. Every time the
1085 are designed to be simple to implement and require only a few lines of
1090 the congestion control mechanisms are not needed.
1164 It should be noted, however, that since small systems running uIP are