>> >The Monitor class is in Excalibur's scratchpad section--awaiting
>> >the soon inclusion
>> >in the main excalibur jar.
>> Sounds very cool. But when you have many resources isn't it dangerous
>> that this collection becomes to big?
>
>They are light-weight resources, and simply wrappers around the
>File you would normally have opened. As the cache removes a
>resource, it would also remove it from the monitor--because we
>no longer have a need to monitor it.
>
>It's main uses would be for the Cache to ensure the resources are
>current, for the configuration files so that Cocoon knows when
>it needs to reconfigure itself, and for generated resources like
>XSP and the Sitemap--which would trigger the rebuilding of the
>resource when the source changed.
Sounds very thinked through, my respect...
Cheers
Gerhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
