[kepler-dev] data caching by actors

[Matt Jones]

Hi Paul,

The EML200Data source actor and the DarwinCoreDataSource actor both
cache data using the Object Manager.  When the EML200DataSource actor
needs to download data, it first checks the cache, and if it is not
found it proceeds to download the data and insert it into the cache.
Subsequent access for that data use the cache, which is located in the
.kepler directory.

Matt

On Tue, Apr 7, 2009 at 4:54 AM, Paul Allen <pea1 at cornell.edu> wrote:
> Could somebody point me to some actors that cache data to make future
> workflow runs more efficient? I know that the provenance framework being
> worked on would require something like this, but I'm wondering if any actor
> has done this on it's own?
>
> I'm just looking for ideas...
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matthew B. Jones
Director of Informatics Research and Development
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara
jones at nceas.ucsb.edu                       Ph: 1-907-523-1960
http://www.nceas.ucsb.edu/ecoinfo
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~