Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 3117 invoked from network); 30 Oct 2007 15:04:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Oct 2007 15:04:57 -0000 Received: (qmail 44213 invoked by uid 500); 30 Oct 2007 15:04:42 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 44131 invoked by uid 500); 30 Oct 2007 15:04:41 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 44122 invoked by uid 99); 30 Oct 2007 15:04:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2007 08:04:41 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2007 15:04:53 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 7D8CA59A07 for ; Tue, 30 Oct 2007 15:04:33 +0000 (GMT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: dev@commons.apache.org Date: Tue, 30 Oct 2007 15:04:33 -0000 Message-ID: <20071030150433.22455.4488@eos.apache.org> Subject: [Commons Wiki] Trivial Update of "VfsCacheStrategy" by OrtwinGlueck X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The following page has been changed by OrtwinGlueck: http://wiki.apache.org/jakarta-commons/VfsCacheStrategy The comment on the change is: typo and english cleanups ------------------------------------------------------------------------------ Every time you call a method on the resolve file object the data will be refreshed with the filesystem. This will give you the behaviour you might expect from a local file but also might be a hughe performance loss as it will greatly increase the network load. - You also can archive this cache strategy if you pack the file object in an {{{org.apache.commons.vfs.cache.OnCallRefreshFileObject}}} + You can also achieve this cache strategy by wrapping the file object in an {{{org.apache.commons.vfs.cache.OnCallRefreshFileObject}}} {{{ FileObject fo = VFS.getManager().resolveFile("...."); OnCallRefreshFileObject foc = new OnCallRefreshFileObject(fo); }}} - the difference to the above is, that in the first case you will always get the same file object instance and thus you can synchronize against it. + The difference to the above is, that in the first case you will always get the same file object instance and thus you can synchronize on it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org