Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1

["Fei Song" <[e-mail]>]

A quick supplement: the etag is also great if file-level conflict is the target~


--------------
Fei Song
>Hi,
>
>>From the previous messages, I think we all agree that the conflict
>resolution should be another layer's problem, whether to enable an
>automatic merging might be a research problem or a further use case. But I
>think the problem belongs to this list is whether we need to detect more on
>the conflicts (not resolving them). Just knowing there are conflicts OR
>knowing what are those conflicts, when and where do they come from (e.g.
>the sequence of different conflict versions). Personally I prefer the
>latter. Just imagine when we reconnect our device and see multiple conflict
>versions but don't know anything about that. How to handle them? Which one
>should we begin with?
>
>IMHO, this is a discussion on which is enough, etag or metadata? Conflict
>detection is just one of the related use cases.
>
>Regards,
>Linhui
>
>2015-12-10 6:08 GMT+08:00 Ted Lemon <[e-mail]>:
>
>> Wednesday, Dec 9, 2015 4:25 PM Jakub Moscicki wrote:
>> > But I would also tend to disagree with your statement that most of files
>> are text files ― as was explained by Marc Blanchet ― in general it is not
>> the case, not only for CERN.
>>
>> I think you and Marc misunderstood what I mean by "text files," but that's
>> immaterial.   Whether merges can be accomplished automatically or not,
>> knowing that a conflict has occurred, and when, and why, is (IMHO)
>> important.
>>
>>
>> --
>> Sent from Whiteout Mail - https://whiteout.io
>>
>> My PGP key: https://keys.whiteout.io/[e-mail]
>>
>> _______________________________________________
>> Storagesync mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/storagesync
>>
>>
>