because the gdbm interface has more restrictive
concurrent-file-access capabilities, the current
container API wont work since it leaves the file open
for read/write during the life of a request.
Logged In: YES
.94c introduces a cache option "cache_nonblocking", the same
as container option "nonblocking", which causes DBMContainer
to open and close the DBM file for each read/write lock with
the corresponding "r" or "w" mode, respectively. without
"nonblocking", the container is just opened as "w" and held
open for the life of the container's namespace manager
(which is the same as the life of the request).
dbm issues as well as synchronization still needs to be
watched on container very closely.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.