GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

2002-06-28 Marcus Brinkmann <marcus@g10code.de>

Browse Source 
* gpgme.texi (Multi Threading): Remove item about the need to
	synchronize anything against gpgme_wait (except gpgme_wait
	itself).
This commit is contained in:
Marcus Brinkmann 2002-06-28 01:14:41 +00:00
parent 3ccd2790b3
commit 92386f4dd1
2 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/ChangeLog
View File

@ -1,3 +1,9 @@
2002-06-28 Marcus Brinkmann <marcus@g10code.de>
* gpgme.texi (Multi Threading): Remove item about the need to
synchronize anything against gpgme_wait (except gpgme_wait
itself).
2002-06-27 Marcus Brinkmann <marcus@g10code.de> 2002-06-27 Marcus Brinkmann <marcus@g10code.de>
* gpgme.texi (Information About Keys): Fix documentation for IDX. * gpgme.texi (Information About Keys): Fix documentation for IDX.

10
doc/gpgme.texi
View File

@ -523,17 +523,9 @@ threads want to deal with the same object, the caller has to make sure
that operations on this object are fully synchronized. that operations on this object are fully synchronized.
@item @item
Only one thread is allowed to call @code{gpgme_wait} at a time. If Only one thread at any time is allowed to call @code{gpgme_wait}. If
multiple threads call this function, the caller must make sure that multiple threads call this function, the caller must make sure that
all invocations are fully synchronized. all invocations are fully synchronized.
@item
Unfortunately, the last rule implies that all calls to one of the
following functions have to be fully synchronized together with
@code{gpgme_wait}, as they call @code{gpgme_wait} internally: All
functions @code{gpgme_op_FOO} that have a corresponding
@code{gpgme_op_FOO_start} function, @code{gpgme_op_keylist_next},
@code{gpgme_op_trustlist_next}.
@end itemize @end itemize