Dirk Meyer wrote: > Hi, > > those who read the cvslog list know that I have some problems with > threading in the kaa.vfs module. After some thinking, maybe using a > thread isn't such a good idea. I used a thread because a reader can > block when the writer writes the db and the writer can block when > there are still readers. The last one doesn't matter, it is only the > server but the first one may be a problem. > > To avoid blocking, the current vfs code uses a little trick. When > calling add_object or update_object, the db is not changed right now > becuase this would block the db until we call commit() the next time.
There may be a second blocking problem: os.listdir could block on discs (spin up) and on network devices. How can we handle that? Do we have to put os.listdir() into a thread for such filesystems? Sounds very ugly to me. Dischi -- The only problem with mornings is that they happen too early in the day.
pgprgCsnnbCjN.pgp
Description: PGP signature
