1) yes
2) probably won't crash but may provide wrong results or ignore images
currently being added
3) no
4) no
These limitations on imgdb.so were one of the key reasons for choosing
Twisted as the python networking library used for exposing the API at
imgdb.so for remote clients. Twisted is aynchronous and event-based so
all remote requests are handled on a single-thread. Making imgdb.so
network-based through this model seemed to me the simplest way to
scale it up without dealing with the complicatioins of multithreading
on C++ code.
I was able to get imgdb.so working under the Equinox OSGi container on
a Linux machine (there are a few issues on different platforms) but
never got around to documenting how to build and wrap it properly or
improving the build files. This was a pre-requisite for building the
Eclipse RCP version of imgSeek which I have stopped working on years
ago. For making imgdb.so working inside the multithreaded world of
complex GUI applications, I'd wrap it on a Java POJO and resort to
Java's thread handling and synchronization mechanisms.
--
Ricardo Niederberger Cabral
http://www.imgseek.net/
ricardo.cabral at imgseek.net
skype: rnc000