I'd like to see uPortal have the ability to cache XML documents used by
channels and a worker of some kind that can refresh the cache in the
background so that user requests do not wait for xml to be retrieved
from badly behaved sites.
Yale has been running such a service for many years - but it is not
entirely stable and I don't think it is a good design. It relies on one
background thread to refresh stale documents based on parameters
passed. It is enormously helpful to the portal's performance to have
shared documents cached and refreshed on a requested interval.
How many other similar implementations are out there to address the
problem of slow or broken external xml dependencies?
Would someone care to recommend or donate a robust and well designed
implementation?
Susan
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
