Ok, so now we have mmcache_lock/unlock() so we can use the API in a thread-safe manner...
But are the functions set by mmcache_set_session_handlers() thread-safe?
It's not that much trouble to make some custom thread-safe session handlers using the mmcache API now that _lock/unlock() are in, though, and I guess not everyone would want sessions to be thread-safe by default.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.