Santiago Gala wrote:
>
> I'm using Observable for tests, but we can change this class by some
> other
> interface if needed after the concept is tested. I will look for similar
> patterns in Turbine/Avalon code.
>
I thought that the Observer pattern was deprecated in Java and a
Listener/Event model was the recommended way of doing things now.
In any case, I think there are several issues with the disk cache system
right now, the main one being that it's over-used throughout the current
jetspeed code, as an interface for accessing remote documents, config files,
etc... We have to stop this !
We should :
1- Define what is the *real* purpose of the DiskCache
IMO, the cache should not try to be as intelligent as it is now
2- Define what kind of repository access we need in Jetspeed
I can see at least 2:
- remote syndicated document repository
- configuration file repository
others ?
3- Define facade class/interface for accessing these repositories
* syndicated document = URLManager service
* configuration files = Persistence service ?
4- Implement these services so that they (don't) use the DiskCache as
they see fit
5- Replace all the other references to the DiskCache in other parts of the
code to references to the appropriate Facade classes.
6- Have a party :)
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
