Hi Ward, Won't this all depends on the TCP state the connection is in when the message is sent? E.g., is Nagle bring turned on? What is the window size? And so on. If you want, one way to understand this better is to look at the messages on wireshark.
Regards KK PS>> OpenFlow ia a protocol that can theoretically be associated with any transport mechanism. You would have an easier time understanding them independently before deciphering their interaction. On 23 May 2011 03:17, Ward hussen <[email protected]> wrote: > HI KK > >>>You do not need to tweak TCP options for this. It is usu. done in an >>> async manner. If you are using a controller like NOX, then this > should not really be of much concern. Are you whipping up a new controller? > > I did not understand the above statement completely. Do you mean that NOX > sends flow_mod packets asynchronously? Does TCP connection not wait for ack > of first FLOW_MOD and then send the 2nd packet? > > If it is asynchrous. Is the TCP connection at NOX just wait for propagation > time for sending second FLOW_MOD? > > thanks, > _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
