From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id A05B3BBAF for ; Wed, 23 Sep 2009 18:26:30 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuADAIDpuUo+FFrDgWdsb2JhbACafAEBFiS8NYQbBQ X-IronPort-AV: E=Sophos;i="4.44,439,1249250400"; d="scan'208";a="33380577" Received: from vtab.com (HELO oden.vtab.com) ([62.20.90.195]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Sep 2009 18:26:30 +0200 Received: from oden.vtab.com (oden.vtab.com [127.0.0.1]) by oden.vtab.com (Postfix) with ESMTP id 0D98E26EF0B; Wed, 23 Sep 2009 18:26:29 +0200 (CEST) Received: from kicki.hq.vtech (kicki.e.vtech [10.40.0.23]) by oden.vtab.com (Postfix) with SMTP id EE88D26EEF9; Wed, 23 Sep 2009 18:26:28 +0200 (CEST) Received: by kicki.hq.vtech (Postfix, from userid 7557) id E840F1B2E80; Wed, 23 Sep 2009 18:26:28 +0200 (CEST) From: "=?utf-8?b?TWF0dGlhcyBFbmdkZWfDpQ==?= =?utf-8?b?cmQ=?=" To: dbm@refined-audiometrics.com Cc: caml-list@inria.fr In-reply-to: <9A577121-0353-4402-924B-F4653AA39016@refined-audiometrics.com> (message from David McClain on Wed, 23 Sep 2009 08:19:37 -0700) Subject: Re: [Caml-list] Cache algorithms: implementation or library available? References: <4AB8A6F1.7090802@inescporto.pt> <4AB8B44F.6040503@ens-lyon.org> <4AB9D439.4070304@inescporto.pt> <21344828-8F8C-457A-98C4-3058D7D6DBAD@inria.fr> <9A577121-0353-4402-924B-F4653AA39016@refined-audiometrics.com> Message-Id: <20090923162628.E840F1B2E80@kicki.hq.vtech> Date: Wed, 23 Sep 2009 18:26:28 +0200 (CEST) X-Virus-Scanned: ClamAV using ClamSMTP X-Spam: no; 0.00; mattias:01 mattias:01 cuoq:01 doligez:01 caml-list:01 algorithms:03 module:03 flush:03 library:03 cfm:95 explanation:06 weak:06 weak:06 implementing:06 acm:08 >> The Weak module is never the right tool for implementing a cache. > >I'm not disputing this, but I would like you hear your thoughts on >this topic. Why? Weak references go away at the whim of the GC, not when it would be useful to flush the cache. A longer explanation and more about weak references can be found in the Cuoq/Doligez article in last year's workshop on ML (http://portal.acm.org/citation.cfm?id=1411308).