"Stanley,Michael P." <[EMAIL PROTECTED]> wrote on 04/03/2003 12:55:56 PM:
> I would like to see things organized in reverse domain names, which > typically would reflect the projects root package. The repository can > be broken down into a series of sub-directories. Gotcha...now I'm getting it. > The idea is we come up with a standard service name - 'mavenrepo' (for > arguments sake). I can set up my DNS record to have -> > _mavenrepo._tcp.mikestanley.org point to a number of different > servers/ports such as mavenrepo1.mikestanley.org:80, and > mavenrepo2.mikestanley.org:8000 I wasn't aware DNS did ports, but ok. > The DNS lookup will resolve _manverepo._tcp.mikestanley.org to whatever > my domain is set up for. I can move the repository, add more servers, > load balance requests, or even move to a completely different domain say > www.ibiblio.com/maven all without forcing any changes in Maven clients > and changes to dependent maven project's project.xml file. How does the client know to talk to _manverepo._tcp.mikestanley.org rather than www.ibiblio.org/maven or whatever else? I thought the idea was to get away from properties files? How do paths like /maven get specified in a DNS entry? > They need to know the projects domain, but not the details of the server > location. Look at the Jabber Protocol dnssrv and s2s service for an > example of how the DNS SRV spec can be used for this type of thing. Ok, will do. > It is very "magic wand"-ish and therefore can be very cool. Cool. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
