Hi,

Couple of thoughts on mirroring third party tools to increase the
build experience.  I like the "put all of the urls in a list" approach,
where urls are in a giant properties file.  I propose we do that and
include a set of mirrors for that list too, so it would look something
like this:

LIB_NAME_VERSION:
http://offical.library.download
http://mirror1.usask.ca
http://mirror2.osna.de

LIB2_NAME_VERSION:
http://offical.library.download
http://mirror1.usask.ca
http://mirror2.osna.de

etc.

This file could be put up somewhere public on our website or in svn or
whatever.  Then we could cron up every night a job that goes through
and throws an error if wget doesn't return a file for each of these.

It also requires matjaz to write a routine to get resources, something
like:

fun getResource(LIB_NAME_VERSION):
  //get a list of the mirrors for this version
  //randomly try one
  //if that one doesn't work remove it from list and repeat
  //when list is empty then throw an error and stop trying

This lets us distribute load "fairly", yet lets anyone shut off their
mirror at any time.  Perhaps we should have the first value the
"principle" location that is always tried first just to keep things
reasonable on our machines.

The issue of copyright and patents deserves a different message so I'd
like to separate this out.  The benefit of doing it this way though is
that we can have multiple mirrors for each library and institutions can
put up or down the mirrors whenever they want.

Chris

-- 
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan

Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
     Department of Computer Science
     University of Saskatchewan
     176 Thorvaldson Building
     110 Science Place
     Saskatoon, SK
     S7N 5C9
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to