What is Session Cache?
When a client/server connect they establish a session ID which it will try to use later. This session id includes what ciphers they agreed upon, etc. A client offers to reuse a session ID. If the server recognizes it then they will skip the whole cipher/etc determination phase, which results in smaller overhead. This is called a cache hit. (the session id cache is where these session ids are.) A session id cache miss means that the client either does not have a session id it can use, or the server does not recognize it. Thus they negotiate ciphers all over again.
Related Questions
- What is the difference between the session notification mode and polling mode? How does that affect the refreshing of the session client cache?
- Does Secure Session or Cache Cleaner detect a second network card for prelogin policy determination?
- How big should I make the cache for a stateful session bean?
