Re: [opendbx] /dev/urandom file descritpors left open, libopendbx-devel Digest, Vol 49, Issue 1
Brought to you by:
nose
From: Norbert S. <no...@li...> - 2014-04-30 22:00:21
|
Hi Adam > 2) We were having major issues with the C++ API crashing the > application when connection objects went out of scope: Did you make a test without using the copy constructor like I've suggested? OpenDBX::Conn GetAllTxFileDb = Conn( "mssql", "172.16.232.60", "" ); > 3) We are calling into the library from multiple POSIX > threads so we MUTEX'ed these calls to allow only one thread at a > time accesses the library. I do not think this is necessary as > your documentation states it is thread-safe however we decided to > do this as an extra precaution. Not every backend is thread-safe but the MSSQL backend is. You can test thread-safety with odbx_get_option( handle, ODBX_OPT_THREAD_SAFE, &value ); Would be interesting if you could find out if using one connection per thread is really thread-safe for the MSSQL backend. This could speed up your application a lot! Remember that in this case you need to call odbx_init(), odbx_bind(), ..., odbx_unbind() and odbx_finish() in each thread. Best regards, Norbert |