[Dev] repo and multiple threads

Morgen Sagen morgen at osafoundation.org
Fri Aug 27 11:44:32 PDT 2004


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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2377 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20040827/88ced6a7/smime.bin


More information about the Dev mailing list