On Mon, Sep 2, 2013 at 12:02 PM, Pascal Obry <[email protected]> wrote:
> 2013/9/2 johannes hanika <[email protected]>:
> > no, that's exactly the race condition horror scenario i described
> earlier..
> > if we write to that file we want to be sure we do that now and only in
> one
> > thread at a time. if you just put it in a job you'll need to provide
> > wrappers which force it to happen now and put a mutex around it etc.
>
> Ok, looks like it was a bad idea to use a background job for this. The
> safety is indeed a very strong point.
>
> Let's drop this then except if you have a better idea to avoid this
> long delay and freeze of the UI.
>
how did you trigger the xmp writing? mark 2k images and tag them at the
same time? that should indeed go into a bg job, where the bg job executes
the tagging and will lock the image only for a short time while it writes
the xmp? we'll need to make sure we write the xmp as part of dropping the
write lock though.
j.
>
> Thanks,
> Pascal.
>
> --
> Pascal Obry / Magny Les Hameaux (78)
>
> The best way to travel is by means of imagination
>
> http://v2p.fr.eu.org
> http://www.obry.net
>
> gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
