Lines Matching full:only

46 The uIP implementation is designed to have only the absolute minimal
47 set of features needed for a full TCP/IP stack. It can only handle a
103 the second kind of requirements will only affect the communication
111 connections. Since there are only very few applications that make use
179 scarce resource. With only a few kilobytes of RAM available for the
203 performance degradation, but only when multiple connections are
205 receiver window, which means that only a single TCP segment will be in
229 provide extremely low throughput and will only allow a small number of
264 for new data. The application program provides only one callback
351 The application can send only one chunk of data at a time on a
353 per application invocation; only the data from the last call will be
412 has been produced. The application can only send data when invoked by
413 uIP, and therefore the poll event is the only way to send data on an
664 the server. Since this is the only data that is sent, the application
917 affect the application state; this should only be done in the acked()
954 The current implementation only has a single buffer for holding
980 only implement ICMP echo messages. Replies to echo messages are
986 Since only the ICMP echo message is implemented, there is no support
1020 only a single TCP segment per connection to be unacknowledged at any
1085 are designed to be simple to implement and require only a few lines of
1088 Since uIP only handles one in-flight TCP segment per connection,
1132 copying, the TCP processing done for an incoming packet involves only
1143 receiver using this algorithm will only send acknowledgments for every
1148 A TCP sender such as uIP that only handles a single outstanding TCP
1150 algorithm. Because the receiver only receives a single segment at a