← Back to team overview

coapp-developers team mailing list archive

Re: [wishlist] [future] Non-webservice fallback for repository XML + mirror requirements

 

I was hoping that the mirroring requirements would be platform agnostic. I
mean come on, downloading, uncompressing and parsing an XML file is hardly a
big deal, especially in managed code.

On Sat, May 22, 2010 at 12:17 AM, Nasser Dassi <nasserd@xxxxxxxxx> wrote:

> Unfortunately, IIRC, most non-Windows-based Web servicing platforms have
> heftier system requirements (software packages, configs, etc) than a
> .NET-based one (which is relatively out-of-the-box).
>
> We should establish the Repository Mirroring requirements.  We should also
> remember that our group objectives are bringing open-source to Windows...
> and not necessarily keeping everything in the Linux portion of the world.
>
> - nasser
>
> On Thu, May 20, 2010 at 9:58 PM, Adam Baxter <voltagex@xxxxxxxxxxxx>wrote:
>
>> Before running away with OData too much, consider the implications of
>> requiring each mirror host to run web services.
>>
>> For the mirror hosts:
>> Most Linux-based packaging systems allow mirroring of the *entire *package
>> tree, and it's no more complex than running (r)sync between mirrors.
>>
>>
>> For the users:
>> Then (especially with signed packages) it doesn't matter *which server*the user wants to point their application at, you get the same packages,
>> faster
>>
>> In some cases, especially in countries with metered connections (Australia
>> et al), this will also allow users to point towards an ISP-supplied, *
>> *unmetered**  mirror.
>>
>>
>> tl;dr
>> Don't make it hard for me to become a CoApp repository mirror.
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
>> Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>

Follow ups

References