It doesn't look like using Session::write() makes the variables available for immediate re-use. This seems counter-intuitive.
{{{
var_dump(
Session::write('test', 'test1'), // false, should be true
Session::read('test'), // null, should be test1?
Session::write('test', 'test2'),
Session::read('test'), // still null, should be test2?
Session::delete('test'),
Session::read('test')
);
}}}
http://rad-dev.org/forks/ddebernardy/lithium/commits/view/b0efcb6302ad107c76c1dc0ad2469350e5191933 fixes the first issue for the PHP adapter. I'd like to get confirmation the above isn't the expected behavior.
also problematic, and certainly related: {{{ Session::write('test', 'test'); var_dump(isset($_SESSION)); // false }}} (That would be when using the default config supplied. The foreach/break in the read()/write() methods makes it prefer cookies.