Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 26805 invoked by uid 500); 6 Dec 2001 09:11:26 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 26792 invoked from network); 6 Dec 2001 09:11:25 -0000 Message-ID: <002f01c17e36$8d1b12a0$5b1114ac@lpernor> Reply-To: =?iso-8859-1?Q?Per-Olof_Nor=E9n?= From: =?iso-8859-1?Q?Per-Olof_Nor=E9n?= To: References: Subject: Re: re-send Excalibur ActiveMonitor Date: Thu, 6 Dec 2001 10:15:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Gerhard Froehlich" To: "cocoon-Dev" Sent: Wednesday, December 05, 2001 3:48 PM Subject: re-send Excalibur ActiveMonitor > Hi, > uninteresting, misspelled, needless or > just overseen? I Saw it, Liked it, Waiting for it. :-) Performance is going to be the nr one issue for choosing cocoon in the end. A powerful tool/framework that can�t scale isn�t going to be found in all the places where it should be. Still, I don�t really know where to put it :-) / Per-Olof > > Cheers > Gerhard > > "EARTH FIRST! We'll strip-mine the other planets later." > > >-----Original Message----- > >From: Gerhard Froehlich [mailto:g-froehlich@gmx.de] > >Sent: Sunday, December 02, 2001 2:06 PM > >To: cocoon-Dev > >Subject: Excalibur ActiveMonitor > > > > > >Hi, > >I think we need to implement the ActiveMonitor > >in the Cocoon Project, to increase the performance > >of Cocoon. > >(I place the mail here in the Cocoon list, > >because it's a Cocoon related topic. But if it's the > >wrong place, I have no problem to move this thread > >into Avalon dev list.) > > > >Berin suggested in the mail: > > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99857216131771&w=2 > >that instead of calling ${file}.lastModified() we asking the > >Excalibur ActiveMonitor if the resource has changed or not. > > > >"Each resource in the collection of resources is tested on a > >frequency you specify (i.e. 1/minute, 1/half-hour, etc). > >That way during extreme load conditions the number of times we > >call the "lastModified" method doesn't change. Instead of 1/request > >(with 200 simultaneous users requesting 4 pages a second > >that comes to 800 calls a second) it is once per period of time." > > > > > >I can't implement this ActiveMonitor from scratch, because > >I have less knowledge of Cocoon internals (was alway in the > >backend ;). So: > >Where is the right place to implement this ActiveMonitor and > >how would you proceed? > > > >Cheers > >Gerhard > > > >-------------------------------------------- > >black holes are when GOD is dividing by zero > >23 49 43 51 3A 20 31 32 33 35 33 34 38 31 31 > >-------------------------------------------- > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > >For additional commands, email: cocoon-dev-help@xml.apache.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org