> One idea is to write a multi-threaded SSL server where each thread
> handles a different connection and stores the data passed over by the
> client. Whether one server is sufficient depends on the time taken to
> establish an SSL session and transfer the data. The data size is about
> 10K and so it seems like the SSL connection time would be a bottleneck.
Don't go thread-per-client. That forces a context switch every time you
change which client you are working on. Better to go single threaded than
force extra context switches. If you want to use threads, use them right
(thread pools, job queues, etcetera).
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
