Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 32728 invoked from network); 21 Oct 2004 18:57:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Oct 2004 18:57:47 -0000 Received: (qmail 39860 invoked by uid 500); 21 Oct 2004 18:57:43 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 39740 invoked by uid 500); 21 Oct 2004 18:57:42 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 39726 invoked by uid 99); 21 Oct 2004 18:57:42 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [217.160.230.41] (HELO mout.perfora.net) (217.160.230.41) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 21 Oct 2004 11:57:41 -0700 Received: from minotaur.apache.org[209.237.227.194] (helo=[127.0.0.1]) by mrelay.perfora.net with ESMTP (Nemesis), id 0MKz5u-1CKi7x3DdV-0006vo; Thu, 21 Oct 2004 14:57:33 -0400 X-Provags-ID: perfora.net abuse@perfora.net e2e4156964dfbcc4c642ec658fa7f9b9 Message-ID: <41780698.3080006@reverycodes.com> Date: Thu, 21 Oct 2004 14:57:28 -0400 From: Vadim Gritsenko User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: FilesystemStore broken??? References: <35311748-22D6-11D9-BEA8-000A95984AEA@betaversion.org> <41772B5E.5080302@reverycodes.com> <3938063D-2379-11D9-891D-000A95984AEA@betaversion.org> In-Reply-To: <3938063D-2379-11D9-891D-000A95984AEA@betaversion.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Pier Fumagalli wrote: > On 21 Oct 2004, at 04:22, Vadim Gritsenko wrote: > >> Store: >> "Clean out" here writes stuff out into the persistent store, >> if stuff is Serializable. >> Transient store: >> "Clean out" here removes stuff completely, hence the >> name: "transient". >> Persistent store: >> Janitor does not touch this store at all. No "clean out" >> happening at all. > > > So, given that the cache is caching in the persistent store, who cleans > it out? The cache itself? This is getting _waay_ to frisky for my taste :-( Cache caches into Store. Store overflows into PersistentStore when low on memory or on shutdown (*). Cache cleans up stale items on "as-detected" basis, or, if you use event cache pipelines, stale items removed as per external events (**). Vadim * Might not work with JCS / EHCache implementations ** Don't know much about this event stuff myself