[EMAIL PROTECTED] wrote:
>
> Raphael Luta wrote:
>
> > 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 ?
>
> These interfaces need to be extensions to the portlet API.
>
I'm not sure of what you mean here. I assume you say that the
service should be compatible with the service-access API which
is (should be) part of the Portlet API. Correct ?
I'm not sure I agree with this statement, but I'd like to make
sure I understood the statement...
--
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]
