[jbosstools-issues] [JBoss JIRA] (JBIDE-19710) Add new caching strategy in URLTransportUtility
[
https://issues.jboss.org/browse/JBIDE-19710?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19710:
-------------------------------------
Hi Fred:
Can you verify the current behavior of CACHE_FOREVER doesn't work for you? My
understanding is that CACHE_FOREVER will still check the remote timestamp before
attempting to download a new one, or will use the local cache. I suspect strongly that
this should fit your usecase and another cache behavior isn't necessary.
Add new caching strategy in URLTransportUtility
-----------------------------------------------
Key: JBIDE-19710
URL: https://issues.jboss.org/browse/JBIDE-19710
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 4.3.0.Alpha2
Reporter: Fred Bricon
Assignee: Rob Stryker
Fix For: 4.3.0.Beta1
Currently, you can use URLTransportUtility like
new URLTransportUtility().getCachedFileForURL(url, "Download stuff", lifespan,
monitor);
with lifespan possible values being :
- URLTransportUtility.CACHE_UNTIL_EXIT : will cache the file during the workspace
session
- URLTransportUtility.CACHE_FOREVER : will cache the file forever once downloaded
In certain cases, we want to be able to use CACHE_UNTIL_EXIT, but also be able to recover
from network outages. So adding something like
- URLTransportUtility.SAFE_CACHE_UNTIL_EXIT (feel free to find a better name) : if the
remote file is available, it will be downloaded on new Eclipse session, if it's not,
the last valid cache will be returned.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)