Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Sep 21 09:08:07 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 m8LG87uv012700 for ; Sun, 21 Sep 2008 09:08:07 -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 m8LGAHff000829 for ; Sun, 21 Sep 2008 09:10:17 -0700 Message-Id: <200809211610.m8LGAHff000829@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Trace File Date: Sun, 21 Sep 2008 09:10:17 -0700 From: Bill Cheng Someone wrote: > In case of traceFileshould we read the values in an array > and then use then use them while further processing > or should we read the values as required? You should read the values as required. The arrival thread can read this one line at a time. Once a customer is created, you can use a field in this customer, say "service_time_from_trace_file", to store the service time from the trace file and have the customer carries this information around. -- Bill Cheng // bill.cheng@usc.edu