Message:
The following issue has been closed.
Resolver: Ben Walding
Date: Tue, 28 Sep 2004 3:44 AM
Done.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVENPROXY-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVENPROXY-18
Summary: move caching to the repository rather than the download engine
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-proxy
Components:
Core
Assignee: Ben Walding
Reporter: Ben Walding
Created: Fri, 24 Sep 2004 8:14 PM
Updated: Tue, 28 Sep 2004 3:44 AM
Description:
Having tinkered and pondered about this, it is now evident that putting caching at the
very front of the proxy is counterproductive. You only really need caching on slow
repositories (slow being up to the user).
Move the caching to the repository and simplify the caching model to
repo.<key>.cache.period=n
(where n is the number of seconds to cache an artifact - 0 disables caching and is the
default).
Remove the overall cache option.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
