[sync] Re: [dev] What should we do about GUIDs changing?

[Mikael Geijer]

Hmm... Let me see where did I hit this issue...you're right, of course 
the client generates it's own GUID's, but it also handles the GUID (or 
LOCURI) from the server. For example when the server sends an <ADD>  the 
server id is sent and the client replis with a <MAP> with it's own id.  
Guess this can be handled with some intelligent mapping on the 
serverside anyway.

Cheers

/Mikael


Anthony Mills wrote:

> AFAIK, It's not an issue.  Clients get to create there own ids, that 
> is why we have to have a mapping to server ids.
>
> Anthony
>
> Mikael Geijer wrote:
>
>> Hi guys.
>> Following your work w interest, don't have time to contribute much 
>> right now. Just wanted to mention that a 32 byte GUID might cause 
>> problems when syncing with some devices. I'm a bit unsure what size 
>> the SYNML-specs recommend - or if the size is negotiated when devinfo 
>> is exchanged. I've seen at least one device with a 12 byte 
>> restriction. Just for your info. Sorry if this makes a mess.
>>
>> Regards
>>
>> /Mikael
>>
>> Chuck Hagenbuch wrote:
>>
>>> Quoting Chuck Hagenbuch <chuck at horde.org>:
>>>
>>>> So, any ideas on a better way to do this? Should we add an extra 
>>>> field for it to all our data stores? I'd rather not, where we can 
>>>> avoid it.
>>>
>>>
>>>
>>>
>>> To update this: Nag, Mnemo, and Kronolith now generate 32-character 
>>> item ids,
>>> and the GUID doesn't include the sharename. All of them are able, at 
>>> least with
>>> the primary backends, to get an item based simply on the GUID (i.e, the
>>> sharename isn't necessary).
>>>
>>>> Though, it occurs to me that the way the code is written, we delete 
>>>> and recreate the task when we move it between tasklists, so that'd 
>>>> have to be fixed too.
>>>
>>>
>>>
>>>
>>> Kronolith, Nag, and Mnemo also all now use a move() method to move 
>>> items between
>>> shares so that the GUID isn't changed. This means that you could 
>>> sync a task
>>> from your PDA to your default tasklist, edit it through Horde to 
>>> include more
>>> information and save it to a shared tasklist, and have the changes 
>>> sync back to
>>> your PDA with no problems, no link being broken, etc. Pretty nifty, 
>>> when we get
>>> there.
>>>
>>> The app I haven't touched is Turba, since it's a bit of a different 
>>> beast. We'll
>>> get to that one when we get there. I'd *really* like some help with 
>>> Turba and
>>> the things that are necessary for syncing, if anyone's interested.
>>>
>>> -chuck
>>>
>>> -- 
>>> "Regard my poor demoralized mule!" - Juan Valdez
>>
>>
>>
>>
>>
>


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=- Mikael Geijer, nufort HB (nufort.net), Oebb AB (oebb.net)
=- mobile: +46 70 7455239 office +46 70 7455239
=- email:  mikael at nufort.net
=- snail:  Kyrklunden 8, 122 32 Enskede, Sweden
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=