MirrorRequest could be enhanced such that it can query the
> source repo for different
> variants (complete,delta,..) of the target artifact, choose the
appropriate
> one, download it, apply
> the post processing steps and store it in the target repo.
>
> Stefan
>
>
>>
et repo.
Stefan
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Pascal Rapicault
Gesendet: Mittwoch, 11. Juli 2007 15:50
An: Equinox development mailing list
Cc: equinox-dev@eclipse.org; [EMAIL PROTECTED]
Betreff: [equinox-dev] Re: [p
15:50
> An: Equinox development mailing list
> Cc: equinox-dev@eclipse.org; [EMAIL PROTECTED]
> Betreff: [equinox-dev] Re: [prov] Deltas for delivering updates
>
> As you correctly identified the separation of responsibility
> between ECF and the provisioning code is done as follow:
>
0
> An: Equinox development mailing list
> Cc: equinox-dev@eclipse.org; [EMAIL PROTECTED]
> Betreff: [equinox-dev] Re: [prov] Deltas for delivering updates
>
> As you correctly identified the separation of responsibility
> between ECF and the provisioning code is done as
I agree with Pascal...I think it's best to keep delta logic out of ECF
if possible.
Identification info could be added to ECF's context (e.g. custom URL
with version info or a new adapter, an associated provider
implementation, etc), but this would at least imply having protocol
support for s
As you correctly identified the separation of responsibility between ECF
and the provisioning code is done as follow:
- ECF is used to do the transports (e.g http, ftp, bittorrent). We
leverage, its API, its transport pluggability (and eventually its ability
to restart downloads).
- The provisionin
