From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 810F5BB83 for ; Mon, 14 Aug 2006 17:48:28 +0200 (CEST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.6/8.13.6) with ESMTP id k7EFmPmw011528 for ; Mon, 14 Aug 2006 17:48:26 +0200 Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA15112 for ; Mon, 14 Aug 2006 17:48:25 +0200 (MET DST) Received: from furbychan.cocan.org (furbychan.cocan.org [80.68.91.176]) by nez-perce.inria.fr (8.13.6/8.13.6) with ESMTP id k7EFmNX7011455 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 14 Aug 2006 17:48:24 +0200 Received: from rich by furbychan.cocan.org with local (Exim 3.35 #1 (Debian)) id 1GCefO-0006jA-00; Mon, 14 Aug 2006 16:47:50 +0100 Date: Mon, 14 Aug 2006 16:47:50 +0100 To: Matt Gushee Cc: caml-list@inria.fr Subject: Re: [Caml-list] Weak hashtables & aggressive caching Message-ID: <20060814154749.GA25793@furbychan.cocan.org> References: <44E08F95.2070105@gushee.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44E08F95.2070105@gushee.net> User-Agent: Mutt/1.5.9i From: Richard Jones X-Miltered: at nez-perce with ID 44E09B49.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 44E09B47.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; hashtables:01 caching:01 caching:01 notepad:01 2006:98 wrote:01 caml-list:01 seems:03 weak:04 problem:05 images:94 implement:06 aug:06 marketing:93 unusable:07 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 On Mon, Aug 14, 2006 at 08:58:29AM -0600, Matt Gushee wrote: > It seems to me it might be useful to implement an aggressive caching > strategy--i.e., since the files to be loaded are known in advance (from > the command line),[...] Please no! When running X remotely this will cause images to be transferred (uncompressed) over the network and stored inside the X server when they may not even be viewed. This sort of thing is already a serious problem with programs like 'eog', making them virtually unusable remotely. Rich. -- Richard Jones, CTO Merjis Ltd. Merjis - web marketing and technology - http://merjis.com Team Notepad - intranets and extranets for business - http://team-notepad.com