Return-Path: william@bourbon.usc.edu Delivery-Date: Sat Oct 4 20:24:53 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m953OrqW030923 for ; Sat, 4 Oct 2008 20:24:53 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m953UIFc022999 for ; Sat, 4 Oct 2008 20:30:18 -0700 Message-Id: <200810050330.m953UIFc022999@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: regarding connection tie break situation. Date: Sat, 04 Oct 2008 20:30:18 -0700 From: Bill Cheng Someone wrote: > I have a question about connection tie break situation. When will that > situation occur? When two nodes "connect" to each other at about the same time. > Will it occur when 2 pairs of hello messages are exchanged? Not necessarily. > For example, > If node 'A' has started listening on a port X. simultaneously it sends > a connect request to node 'B'. Now node 'B' started listening on a port > Y,and simultaneously it sends the connect request to node 'A'. Till now > they have just send connect requests, no one has sent "hello" message. Exactly! This is the condition I mentioned above. > So, should they circulate 4 hello messages and decide which of the 2 > connection should stay and which should exit (depending on the port > number and host address)? Not necessarily. From A's point of view, as soon as it gets a HELLO from either connection, it should be able to decide which connection to kill. -- Bill Cheng // bill.cheng@usc.edu