Return-Path: william@bourbon.usc.edu Delivery-Date: Wed Apr 18 07:46:27 2007 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, NO_REAL_NAME autolearn=ham version=3.1.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.13.5/8.13.5) with ESMTP id l3IEkR1m031056 for ; Wed, 18 Apr 2007 07:46:27 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.13.5/8.13.5) with ESMTP id l3IEkS0U013476 for ; Wed, 18 Apr 2007 07:46:28 -0700 Message-Id: <200704181446.l3IEkS0U013476@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Question about buffer limits Date: Wed, 18 Apr 2007 07:46:28 -0700 From: william@bourbon.usc.edu Someone wrote: > Is it reasonable to assume that the only messages that will ever be > larger than the 8192 byte buffer limit are STORE and GET RESPONSE, > and that within those messages only the actual file data will ever be > larger than 8192 bytes (i.e. not the metadata or certificate)? Yes. I think metadata and certificates are much smaller than that. -- Bill Cheng // bill.cheng@usc.edu