Bug in session_write function
The pgsql_session_write function has a flaw -- it relies on pgsql_session_read to INSERT the database row.
While pgsql_session_read() is called before pgsql_session_write() 99.9% of the time, there's one case in which this doesn't happen -- when session_regenerate_id() is called. PEAR_Auth calls this function, rendering it incompatible with this package.
Fortunately, the fix is simple:
add a call to pgsql_session_read($key) to pgsql_session_write().
To make my self more clear:
It does update in one transaction, great, but if you happen to be loading two pages with same session at the same time you lose changes by one of them on update. Quick solution might be just to wait until the first page is finished... this may happen with frames and with users browsing with more than one window, especially when the server is a bit loaded or you are doing something slow on one of the browsers..
Only that I'd like to rather have session handler as a module (is this possible ?).
Some locking to allow safe clustering would be nice, and enable one to use it for corporate-class applications..
A fast application server for .NET and Mono.
A set of tools for a variety of purposes.