Re: Repository Distribution via DNS

2006-10-25 Thread Carlos Sanchez
On 10/24/06, Brian Topping <[EMAIL PROTECTED]> wrote: With the snapshots repo down, there was some discussion on IRC. Joakim mentioned there was some discussion of a resolution that was "DNS-like, not actual DNS" and it got me thinking DNS might be a better solution (possibly with RFC-2782 exten

Re: Repository Distribution via DNS

2006-10-24 Thread Brian Topping
On Oct 24, 2006, at 2:22 PM, Dan Fabulich wrote: I don't think I understand the details of what you're proposing here, but it sounds like you're thinking that the "foo" organization would set up maven.foo.org, and that Maven would automatically fall back to checking maven.foo.org if the cen

RE: Repository Distribution via DNS

2006-10-24 Thread Dan Fabulich
Comments below Brian Topping wrote: > 2) Authenticity of artifacts is validated by control of DNS. The > current method of getting an artifact into the central repository > isn't scalable. If you know someone well enough, they put your code > into the repository. If you don't know someone, your

Re: Repository Distribution via DNS

2006-10-24 Thread Jason van Zyl
On 24 Oct 06, at 3:18 PM 24 Oct 06, Brian Topping wrote: With the snapshots repo down, there was some discussion on IRC. Joakim mentioned there was some discussion of a resolution that was "DNS-like, not actual DNS" and it got me thinking DNS might be a better solution (possibly with RFC

Re: Repository Distribution via DNS

2006-10-24 Thread Shane Isbell
If you use DNS for fault-tolerance, if one repo goes down, it may take upwards of 15 minutes for the client side DNS cache to clear and use the new IP: this may be acceptable, depending on your requirements. A more reliable approach would be to use a load balancer to ping the distributed caches an