On Sat, Mar 22, 2014 at 12:28:16PM -0400, Larry wrote:
allowing dynamic allocation so that every server remains independant.
Since this does not consume that much of resources, we can easily allocate
even 50Mo for the shared memory without any fear.
Before I start coding, I would like to know if there are any mistakes in
the idea. I may have missed something huge.
Did I ?
You may have better luck adding replication logic to the session
cache.
The idea of replication of shared memory looks utterly broken, in
particular as there are pointers stored in shared memory (take a
look at ngx_ssl_new_session() for details).
On Sun, Mar 23, 2014 at 06:50:18AM -0400, Larry wrote:
And if so, why ssl ticket (rfc 5077) even exists ?
Both session cache and session tickets are needed to reduce cost
of creating of new connections. It’s not something mandatory,
rather an optimization.