> Right on !
>
> May I ask a silly question?
> Why would you do such a weird thing in the first place? (maybe we should
> have started from there) :)
Because you might have a design where you have a pool of I/O threads and a
queue of I/O jobs. Read jobs and write jobs might be thrown into the same
queue, so it's possible two threads might get a job for the same connection
in the opposite direction. Usually you fix this by having one mutex for each
connection and protecting the calls to reads/writes by that connection
mutex. However, if you're primarily designing for OpenSSL connections, then
you probably would just consolidate the jobs into 'read job', 'write job',
'read and write job', and only allow one job per connection.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
