Adam R. B. Jack wrote:
Mark R. Diggory [EMAIL PROTECTED] wrote:
ASF Repository:
About this time what I'm maintaining is the following two repository
directories:
Thanks for this write-up.
I haven't yet explored the idea of getting a repository.apache.org
virtual host going. Up
Erik Abele wrote:
I suspect their views would include what you suggest, that
distribution might
save some nomimal (c.f. artifact sizes) bandwidth savings give some
CPU
saving, but it'd be at significant loss of 'control' (of well behaved
clients). Central control over this seems the most
Adam R. B. Jack wrote:
Ought we simple download it using Download-Manager w/ trusted? :)
Ought we not simple copy it down to the local repository location?
- copy file to a tmp-Directory with tmp-Name
- check tmp file to MD5
- if correct, copy tmp file to local repository with correct name
Sorry for the later response, currently, I think the major issues are in
managing the content of java-repository in responsible manner.
Key issues I can see needing to be addressed are the following.
1.) Get projects to be as responsible for their content in
java-repository as they are for the
://www.faqs.org/rfcs/rfc1321.html
A hard fast dig through the RFC suggests a loophole here as there is
no reference to what the contents of a md5 signature fle should look
like. Seems more of a inherant suggestion in the implementation itself.
-Mark
Mark R. Diggory wrote:
Its a tough call, is there any
