Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 26635 invoked from network); 6 Apr 2005 21:37:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Apr 2005 21:37:15 -0000 Received: (qmail 1922 invoked by uid 500); 6 Apr 2005 21:37:09 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 1911 invoked by uid 500); 6 Apr 2005 21:37:09 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 1898 invoked by uid 99); 6 Apr 2005 21:37:09 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of comfortable.numb@gmail.com designates 64.233.184.199 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.199) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 06 Apr 2005 14:37:09 -0700 Received: by wproxy.gmail.com with SMTP id 71so371335wri for ; Wed, 06 Apr 2005 14:37:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=rbfBqYo0AX7zU62b+kIIx3HIpWbP5S717w7h18sNQNZLZ5C8NzIx61Rj+Ahns15HFyVkAfEvmsZbKK0y8oaWWNhOqRYREvc9p3nLAhg6z7eUgudntpzhaO+1iKWidhiGhm/ecc3J7U9HSGJtPg9GpBXIuPkiePAOPirixnb/HFc= Received: by 10.54.76.3 with SMTP id y3mr502007wra; Wed, 06 Apr 2005 14:37:07 -0700 (PDT) Received: by 10.54.70.17 with HTTP; Wed, 6 Apr 2005 14:37:07 -0700 (PDT) Message-ID: <3177d25505040614375f06815e@mail.gmail.com> Date: Wed, 6 Apr 2005 17:37:07 -0400 From: Soaring Eagle Reply-To: Soaring Eagle To: Jakarta Commons Users List Subject: Re: Configuration - Reload Strategy in j2ee containers In-Reply-To: <425449B6.70308@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <4251B5FE.6080606@gmail.com> <3177d25505040607194ec611f5@mail.gmail.com> <4254310F.101@gmail.com> <3177d255050406123345491752@mail.gmail.com> <42543C2C.8030701@gmail.com> <3177d255050406130849fc719@mail.gmail.com> <425449B6.70308@apache.org> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks Emmanuel. But how does commons cache this timestamp? If it is a singleton, how does commons ensure that the instance is always in memory? For example, such a time interval could be set to many days (concievably). How do ensure that the instance is not garbage collected before the interval arrives? On Apr 6, 2005 4:42 PM, Emmanuel Bourg wrote: > Soaring Eagle wrote: > > > How does commons configuration determine when the interval is done > > without caching at least the timestamp of the last read? In other > > words, without threading, how does commons cache any data? If I know > > how, then I will surely use this feature from commons rather than > > writing my own logic. > > Commons Configuration keeps the timestamp of the last file check. On > accessing a property (by calling getString(), getInt(), etc), the file > is checked again if a specified delay is elapsed since the last check. > Of course the configuration is not reloaded after this delay if the file > didn't change. > > Emmanuel Bourg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org