Lines Matching full:should

124 should be invoked by the main control loop. The input handler function
127 produced one or more reply packets which should be sent out. If so,
128 the network device driver should be called to send out these packets.
133 the periodic timer should fire, it should invoke the timer handler
136 driver should called to send out the packets that may have been produced.
141 architecture on which uIP is intended to run. These functions should
223 traffic the system should be able to handle and the maximum amount of
286 the retransmission. When uIP decides that a segment should be
296 to know when the retransmission should be made. Thus the complexity of
319 which service the connection should provide. For instance, an
348 for producing the actual data that should be sent, the packet buffer
361 should be made. As uIP does not keep track of packet contents after they have
364 retransmission. When uIP decides that a segment should be
377 should be made. Thus the complexity of the application does not
483 configuration variable UIP_APPCALL should be defined to be
523 complexity is that if data should be lost in the network, the
605 If the system should run multiple applications, one technique to
666 should be retransmitted. It is therefore possible to combine these two
731 The application state consists of a pointer to the data that should be
798 for the connection. Since it may be the case that data should be sent
908 because of inactivity, or when a retransmission should be made. The
913 after checking if data should be sent out or not as indicated by the
916 It is important to note that the senddata() function never should
917 affect the application state; this should only be done in the acked()
1048 should be made.
1053 retransmission. When uIP decides that a segment should be
1063 to know when the retransmission should be made. Thus the complexity of
1164 It should be noted, however, that since small systems running uIP are