Re: EAP TLS cache help

Future releases will work better here >(3.1 / 4.0). We've moved away from >using OpenSSL's crappy cache, and >written our own. To our (non) surprise, >our code works better. A lot better. >And SSL sessions can then be cached in >memory, disk, memcached, redis, ...

This is one reason we are on 3.1.x (and looking forward to 4.x :) ) alan