Topic: NO_SESSION_CACHE
I noticed this is an option in ssl.c. What are the pro/cons of defining this flag?
You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → wolfSSL → NO_SESSION_CACHE
I noticed this is an option in ssl.c. What are the pro/cons of defining this flag?
Pros: Not having to implement the OS specific locking/unlocking of the session cache mutex in a multi-threaded environment.
Cons: For the client the con isn't too bad unless the client would otherwise be doing a lot of session resumptions and/or there are device constraints making public key operations extremely slow on the device. For the server, the cons are pretty big unless there are a low number of clients and they aren't doing session resumption.
wolfSSL - Embedded SSL Library → wolfSSL → NO_SESSION_CACHE
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.016 seconds (90% PHP - 10% DB) with 10 queries