Rapha�l Luta wrote:
> There 3 issues, which IMO should be clearly separated in Jetspeed :
I totally agree with that - we really have to differentiate between the
different kinds of caching. It should be possible to configure different
cache service implementations for these different kinds of caching.
> - the caching needs of the layout system for optimizing performance
> (mainly in memory resource and content caching). This should not
> care about remote URLs or content write access concurrency
> - resource content management and integrity preservation.
> This complex issue should be addressed by a dedicated content
management
> system (I know at least 2 such OSS project: Prowler and Slide, both
Apache
> or Apache compatible). Jetspeed should define a content management
interface
> for plugging to these systems for handling complex cases and provide a
simple
> content management implementation for the out-of-the-box evaluation
purpose
> or small load sites.
> - syndication caching
> Can be thought of as an extension of the content management issue but
has
> some specific issues (mainly managing relations with the syndicators).
> Those interested in exploring the full scope of syndication issues may
have
> a look a the ICE specification...
Best regards,
Thomas
Thomas Schaeck
IBM Pervasive Computing Division
Phone: +49-(0)7031-16-3479 e-mail: [EMAIL PROTECTED]
Address: IBM Deutschland Entwicklung GmbH,
Schoenaicher Str. 220, 71032 Boeblingen, Germany
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
