A Cache should not be responsible for storing, should it? Then it isn't
a cache, but a DB...
I recommend to use some Storage interface for cache. You will be very glad
then you will decide at later time to store your applications state to
stable Storage, add transactions .
And even if
Jep, and I do the same in my app, but a layer lower (_not_ in the cache,
but in the DB layer, which is the persistency layer I described above).
It may interesting for you if you do the same in your app.
I use cashe this way:
//implementation of StorageCacheHelper not the last
-Original Message-
From: Juozas Baliuka [mailto:[EMAIL PROTECTED]]
Sent: woensdag 16 januari 2002 13:49
To: Jakarta Commons Developers List
Subject: RE: [simplestore] inital check in
Jep, and I do the same in my app, but a layer lower (_not_
in the cache,
but in the DB layer
Subject: RE: [simplestore] inital check in
Hi,
I read documentation tested all Reference types today.
The problem exists, object is cleared before reference is queued.
There is no way to flush expired object to stable storage if it has no
strong references,
but you can solve it this way
:
15.01.2002 Subject: RE: [simplestore] inital check
in
13:46
-Original Message-
From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
Sent: zaterdag 12 januari 2002 18:12
To: Jakarta Commons Developers List
Subject: [simplestore] inital check in
Hi all,
I just booked in the first version of the simplestore
into the sandbox area.
[...]
[EMAIL PROTECTED] To: Jakarta Commons
Developers List
t
[EMAIL PROTECTED]
cc:
15.01.2002 Subject: RE: [simplestore]
inital check in
13:46
-Original Message-
From: Juozas Baliuka [mailto:[EMAIL PROTECTED]]
Sent: dinsdag 15 januari 2002 18:37
To: Jakarta Commons Developers List
Subject: RE: [simplestore] inital check in
Hi,
I think simple store is too simple :).
I see some things to do for simple store.
[...]
4
Commons
Developers List
t
[EMAIL PROTECTED]
cc:
15.01.2002 Subject: RE: [simplestore]
inital check in
13:46
Please
respond
-Original Message-
From: Tom Klaasen (TeleRelay) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 6:06 PM
To: Jakarta Commons Developers List
Subject: RE: [simplestore] inital check in
-Original Message-
From: Juozas Baliuka [mailto:[EMAIL PROTECTED]]
Sent: dinsdag
-Original Message-
From: Juozas Baliuka [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 3:34 AM
To: Jakarta Commons Developers List
Subject: Re: [simplestore] inital check in
StoreJanitorImpl: you can register your Memory Stores in
this class. A background Thread
Hi,
persistence + Cache is one of the most common problems, in web applications.
And I think recenmtly used algorythm is the best solution for this kind
of cache.
I saw a lot of cache implementations, but all of them implements
Background Cleanup
this way: Thread checks memory usage, object
Aaron,
From: Aaron Smuts [mailto:[EMAIL PROTECTED]]
Hi:
How do you find JISP? I added a disk auxiliary cache to JCS that uses
it and it seems pretty fast and I haven't been able to get it to lock
up. It uses a lot of disk space and doesn't take kindly to sharing
files. I haven't tried to
Juozas,
From: Juozas Baliuka [mailto:[EMAIL PROTECTED]]
StoreJanitorImpl: you can register your Memory Stores in
this class. A background Thread checks if memory running
slow in you JVM and if yes it frees some objects out of the
registered Stores.
Hi,
I think it is better to use
Sorry I mistook a typo slow for low. I looked over the code.
Aaron
-Original Message-
From: Aaron Smuts [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 13, 2002 8:35 PM
To: 'Jakarta Commons Developers List'
Subject: RE: [simplestore] inital check in -- cache (JCS plugins
StoreJanitorImpl: you can register your Memory Stores in
this class. A background Thread checks if memory running
slow in you JVM and if yes it frees some objects out of the
registered Stores.
Hi,
I think it is better to use java.lang.ref.* to solve problems related to
memory management.
16 matches
Mail list logo