Re: locking foo ...

On Wed, 2013-12-04 at 12:13 +0200, Noel Grandin wrote:
> On 2013-12-04 11:38, Michael Meeks wrote:
> >     Of course, an alternative might be to have a "GUI thread" that does
> > nothing but run a main-loop, never executing any code - such that we can
> > always safely yield, and/or create/destroy windows/GCs etc.
...
> Wasn't the idea that
>
> (a) we were going to gradually migrate to running everything on the same thread,

        Well - this would be ideal of course =)

> (b) except for the handful of places where parallelism is truly beneficial

        And there are a number of those particularly in import / export.

> (c) and for those parallel places, each parallel chunk would live in it's own
> little island, interacting as little as possible with the main thread.

        Which of course is an ideal way to do threading =)

> Or am I merely projecting my own design ideas onto the past discussions :-)

        Sure - the question really is how best to deal with the mess we have
currently. It's not entirely clear that the above scenario is even
achievable with the functionality we've exposed to eg. scripting / Java
users today =) someone needs to sit down and carefully work through
every threading use-case, and use of the SolarMutex across all the code.
Then they need to unwind the UNO appartment model (which was originally
intended to be some sort of solution here), and finally all the platform
toolkit's thread safety / affinity & functionality in this area - which
is really not a trivial task.

        When we have all of that understood - at least in one brain, we can
(perhaps) work out what to do for the best =)

        ATB,

                Michael.

-- 
 michael.meeks@collabora.com  <><, Pseudo Engineer, itinerant idiot