#7 container API doesnt support gdbm

closed-fixed
cache (3)
7
2004-10-20
2004-10-20
Mike Bayer
No

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.

Discussion

  • Mike Bayer

    Mike Bayer - 2004-10-20
    • status: open --> closed-fixed
     
  • Mike Bayer

    Mike Bayer - 2004-10-20

    Logged In: YES
    user_id=1100624

    .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.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks