Re: libct ct_connect thread_safe

On Dec 15,  9:17pm, [email protected] (Peter Deacon) wrote:
-- Subject: Re: [freetds] libct ct_connect thread_safe

| Reminds me OpenSSL is a bit weird in that you have to register your own 
| synchronization callbacks (reader/writers) in order for SSL to be 
| thread safe.
| 
| Even if you keep connections in their separate threads there is still a 
| little bit of shared state to manage the caches for SSL session resumption 
| in the client.  Given TDS connections tend to be relatively long lived it 
| is very hard to get this sort of synchronization bugs to materialize in 
| real life.  It can creep up if your app is making lots of new connections 
| concurrently.
| 
| Does anyone have a problem with assuming pthread_rewlock_* is available 
| on UNIX systems where TDS_HAVE_PTHREAD_MUTEX is defined?

You mean pthread_rwlock_*? I think yes, since both pthread_mutex and
pthread_rwlock are both specified in IEEE Std 1003.1-2001 (aka POSIX.1).

christos