Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 90047 invoked from network); 16 Dec 2010 14:16:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Dec 2010 14:16:38 -0000 Received: (qmail 20745 invoked by uid 500); 16 Dec 2010 14:16:38 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 20655 invoked by uid 500); 16 Dec 2010 14:16:36 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 20647 invoked by uid 99); 16 Dec 2010 14:16:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Dec 2010 14:16:35 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of heavy@ungoverned.org designates 67.222.39.60 as permitted sender) Received: from [67.222.39.60] (HELO oproxy2-pub.bluehost.com) (67.222.39.60) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 16 Dec 2010 14:16:28 +0000 Received: (qmail 20331 invoked by uid 0); 16 Dec 2010 14:16:07 -0000 Received: from unknown (HELO host118.hostmonster.com) (74.220.207.118) by oproxy2.bluehost.com with SMTP; 16 Dec 2010 14:16:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=ungoverned.org; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=Z2rtZM2ZYIX0HC36P9d6HMoIq5809JCwoWFG2wakAUehEI8VW9rcsL9+4PIp5wRLWRSCyZj2+v9II1J1gOPT34EMpzsMPWiCyT811lkp8TuCGJBLkc67Z2ccgyQwBiap; Received: from adsl-99-62-222-230.dsl.sgnwmi.sbcglobal.net ([99.62.222.230] helo=heavyweight.glastender.com) by host118.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1PTEcp-00009o-D0 for dev@felix.apache.org; Thu, 16 Dec 2010 07:16:07 -0700 Message-ID: <4D0A1F25.40300@ungoverned.org> Date: Thu, 16 Dec 2010 09:16:05 -0500 From: "Richard S. Hall" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: dev@felix.apache.org Subject: Re: Q regarding ExecutionEnviroment References: <20101215124753.5FF3.8BA051B2@lab.ntt.co.jp> <4D08CA83.6000706@ungoverned.org> <20101216103132.6047.8BA051B2@lab.ntt.co.jp> In-Reply-To: <20101216103132.6047.8BA051B2@lab.ntt.co.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Identified-User: {1027:host118.hostmonster.com:ungovern:ungoverned.org} {sentby:smtp auth 99.62.222.230 authed with heavy@ungoverned.org} On 12/15/10 20:31, Ikuo Yamasaki wrote: > Hi Richard, > > Thank you for your comment. > > On Wed, 15 Dec 2010 09:02:43 -0500 > "Richard S. Hall" wrote: > > Richard> On 12/14/10 22:47, Ikuo Yamasaki wrote: > Richard> > CDC Foundation Profile 1.1 > Richard> > Richard> We don't test on it regularly, but we try to not use recent Java > Richard> features, so it should and if not, you can report issues. Currently, > Richard> there is this outstanding issue: > Richard> > Richard> https://issues.apache.org/jira/browse/FELIX-2700 > > That is the issue I have encountered !! You can use 3.0.5 as a work around for now. > Richard> This was the result of a recent change, so we'll introduce a > Richard> configuration property to disable cache locking for smaller VMs. > > Q1. Is my understanding correct ? > - After introducing the configuration property, the Felix framework will > be able to run on CDC FP1.1. However, in that case, "cache locking" > feature will be missed. File locking will be enabled by default, you will need to disable it on Foundation. Yes, the feature will be missed. However, we survived 10 years without it, so I doubt it will be missed. :-) > Q2. Could you tell me about "cache locking" feature ? > (What will be a problem in CDC FP1.1 case?) Nothing. Just don't configure two frameworks to use the same bundle cache. > Q3. When will the configuration property be introduced ? > (Do you have any timeline ?) Next micro release. Hopefully in a week or two. Use 3.0.5 for the time being...or comment out the feature and build your own snapshot from trunk. -> richard > Best regards, > > > Richard> > Richard> -> richard > Richard> > Richard> > > ======= > Ikuo YAMASAKI > >