Skip Menu |
 

Subject: tweak kdb interface for thread safety
Drop the flag in the data structure that says whether the interface is
thread-safe; the plugin should always be thread-safe. The kdb library
should drop the lock support related to this, too.
From: raeburn@mit.edu
Subject: CVS Commit
Remove the thread-safety flag from the kdb plugin interface. Instead,
have the kdb code assume the plugin is thread safe, and implement some
quick and dirty wrapper functions in the db2 plugin to make it use a
local mutex.

There's still some mutex code in the kdb library that should be
reviewed, and simplified or removed.


Commit By: raeburn



Revision: 17611
Changed Files:
U trunk/src/lib/kdb/ChangeLog
U trunk/src/lib/kdb/kdb5.c
U trunk/src/lib/kdb/kdb5.h
U trunk/src/plugins/kdb/db2/ChangeLog
U trunk/src/plugins/kdb/db2/Makefile.in
U trunk/src/plugins/kdb/db2/db2_exp.c
U trunk/src/plugins/kdb/db2/kdb_db2.h
From: raeburn@mit.edu
Subject: CVS Commit
Delete the rest of the support in the kdb library for doing locking on
behalf of the plugin library. Convert the remaining locking code (for
protecting the list of plugins loaded) to use the k5_ macros.


Commit By: raeburn



Revision: 17612
Changed Files:
U trunk/src/lib/kdb/ChangeLog
U trunk/src/lib/kdb/Makefile.in
U trunk/src/lib/kdb/kdb5.c
U trunk/src/lib/kdb/kdb5.h
Done.