[Dev] repo and multiple threads

[John Anderson]

This has been a problem for a long time and I don't think we have a very 
good solution -- Stuart has also struggled with the problem. Perhaps a 
notification could be sent that can be picked up by the UI thread and 
acted upon. However, another solution would be to share the repository 
view, which doesn't require seperate threads, but you'll have to deal 
with the concurrent access issues.

John

Morgen Sagen wrote:

> I understand that thread A doesn't see thread B's changes until both B 
> and A commit( ).  Do we have a mechanism in place (or at least thought 
> about) for allowing thread B to inform thread A that it needs to 
> commit( )?  I think we may be running into this situation now:  when 
> the user modifies their IMAP settings in the main thread and commits, 
> how does the imap client code actually see those modifications?  It 
> won't pick up the modifications until after the imap thread does a 
> commit( ) -- which it may not do right away.
>
>------------------------------------------------------------------------
>
>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
>Open Source Applications Foundation "Dev" mailing list
>http://lists.osafoundation.org/mailman/listinfo/dev
>  
>