Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Oct 31 07:41:40 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.4 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 m9VEfe32017647 for ; Fri, 31 Oct 2008 07:41:40 -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 m9VErVQA027707 for ; Fri, 31 Oct 2008 07:53:31 -0700 Message-Id: <200810311453.m9VErVQA027707@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: prompt at startup Date: Fri, 31 Oct 2008 07:53:31 -0700 From: Bill Cheng Someone wrote: > When our program just launched, do we have to show prompt > immediately? You mean like within 1 millisecond? There is no such requirement. But you should show the prompt and ready to accept user command when all threads *on this node* are up and running. > We plan to show prompt until every node is joined the network, > because it's possible that user enter status command but network > is not constructed. > Which way is correct? We have a peer-to-peer network, you may never know when every node has joined the network. Also, it's expected that some nodes will be down, although you are not suppose to know which ones. So, you should not wait as you are suggesting. -- Bill Cheng // bill.cheng@usc.edu