[Sugar-devel] Datastore API changes (was: Re: Journal --- Sugar-Developers meeting REMINDER (2 July, 2009 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting)
Tomeu Vizoso
tomeu at sugarlabs.org
Thu Jul 2 10:14:36 EDT 2009
On Thu, Jul 2, 2009 at 15:10, Bert Freudenberg<bert at freudenbergs.de> wrote:
>
> On 02.07.2009, at 14:52, Sascha Silbe wrote:
>
>> On Thu, Jul 02, 2009 at 11:52:01AM +0200, Bert Freudenberg wrote:
>>
>>>> [1] http://git.sugarlabs.org/projects/versionsupport-project/repos/mainline/blobs/master/datastore-redesign.html
>>> How do you intend transfer of file ownership to be handled?
>>
>> checkout:
>> * data store hardlinks entry into target directory
>> * files read-only and directories read-write for activity (=>
>> ensure link-breaking)
>>
>> Commit is similar, now mentioned in the document as well.
>
> That means the activity is responsible for deleting the file it
> committed once the DS is finished? That's a burden on activity
> developers the previous DS did care of. If at all possible, cleaning
> up should be left to the DS.
Also copying a file can be quite expensive, specially on the XO-1. If
we are going to have a slow commit operation, we may need a way to get
progress so we can expose it in the UI.
Regards,
Tomeu
> Also "activities should not submit new entries while the previously
> submitted one hasn't been fully committed yet" would be another
> burden. If an activity needs to store a couple of items it would have
> to queue the write commits and issue them one by one? That would be a
> silly requirement, in particular since the DS needs to work on commits
> simultaneously anyway (because two activities might commit at the same
> time).
>
> - Bert -
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
More information about the Sugar-devel
mailing list