Merging of collections

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Merging of collections

Werner Donné

Hi,

RFC 3253 says that if the merge source identifies a VCR, the checked-in
version of that VCR is the merge source. This doesn't seem to cover
the classical case where a labeled version in one branch is merged into
another branch. Allowing the Label header in the MERGE method could
solve this. This way the request URI and the merge source could be the
same VCR, where the version with the label is the merge source.

Regards,

Werner.
--
Werner Donné  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Merging of collections

Geoffrey M Clemm

Yes, that would be a reasonable optimization.  
Currently, that would require two round-trips ... one to retrieve the version with that label, and another to do the MERGE.

Cheers,
Geoff


Werner wrote on 11/20/2006 05:57:35 AM:
> RFC 3253 says that if the merge source identifies a VCR, the checked-in
> version of that VCR is the merge source. This doesn't seem to cover
> the classical case where a labeled version in one branch is merged into
> another branch. Allowing the Label header in the MERGE method could
> solve this. This way the request URI and the merge source could be the
> same VCR, where the version with the label is the merge source.