Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 65701 invoked by uid 500); 21 Nov 2001 10:57:51 -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 65690 invoked from network); 21 Nov 2001 10:57:51 -0000 From: "Carsten Ziegeler" To: Subject: RE: [PATCH] MRUMemoryStore and fellows fixes Date: Wed, 21 Nov 2001 11:59:21 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-reply-to: X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 21.11.2001 11:58:02, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 21.11.2001 11:58:03, Serialize complete at 21.11.2001 11:58:03 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Gerhard Froehlich wrote: > > > >I'm currently incorporating your patches (Startable interface). > >For this I have to change some component handling. > >I will finish this in 1h (aprox) and then you can add > >your filtering easily. > > Was it wrong, the way I implemented it? > The implementation of the MRUMemoryStore and the FileysystemQueueImpl was not correct since a long time. They looked up some components but never released them. The second thing is: As far as I know, you don't have to call the start() or stop() method of a Startable component itself. It's done by the ComponentManager. PS: I will check-in the patches right now. Carsten > >> > >> >thanks for your patch! But - sorry for this pain - > >> > >> autsch ;) > >> > >> >I think we should not change existing interfaces > >> >like the Store interface. > >> > >> I know you would say, that. For my defence I didn't > >> wanted to change the FilesystemStore. I did it once > >> and got - well - in trouble. > >> > >> >The MRUMemoryStore calls the keys() method > >> >of the FilesystemStore. The fsstore returns > >> >all keys, but only those contained in a special > >> >directory are of interest. > >> > >> That would be nice. > >> > >> >What do you think of filtering the keys() > >> >delivered by the fsstore in the MRUMemoryStore? > >> >I know this is slow but would allow us to keep > >> >the interface. > >> > >> Yes that would be a solution. The next Problem > >> are this two Enumerations. I did a awful hack > >> to megre them together. Maybe you know a better > >> solution. > >> > >> >In addition the keys() method of the fsstore > >> >is wrong as it doesn't go into directories. > >> >I will fix this asap. > >> > >> Ok then I can implement the filter. > >> > >> Cheers > >> Gerhard > >> > >> > > >> >Carsten > >> > > >> >Gerhard Froehlich wrote: > >> >> > >> >> > >> >> Hi, > >> >> as promised this patch contains serveral fixes > >> >> in the store implementation: > >> >> > >> >> MRUMemoryStore: > >> >> - added Disposable interface and implemented > >> >> the initialize() and dispose() method to init- > >> >> ialize/dispose the StoreJanitor and the FilesystemQueue > >> >> thread. > >> >> - completed the methods containsKey() and keys() > >> >> (I needed to extend the Store interface and the > >> >> FilesystemStore too) > >> >> > >> >> StoreJanitor: > >> >> - added the Startable interface and implemented > >> >> start() and stop() to start/stop the checker > >> >> thread > >> >> > >> >> FileSystemQueue: > >> >> - added the Startable interface and implemented > >> >> start() and stop() to start/stop the writer > >> >> thread > >> >> > >> >> 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 > > > > > > > --------------------------------------------------------------------- > 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