I'm also interested in solutions for such scenario. Brgds Viktor
On 6/16/09, Lorenzo Fiorini <[email protected]> wrote: > Today I've released my first 2.0.0beta1 based binaries to a selected > customer. > Now I can start to introduce threads in the code and the idea is to > start with long lasting tasks like reports. > > I'm looking if there is a way to clone the workareas instead of > reopening all the dbfs when the thread is started. > > I've found a msg from Przemyslaw that says: > --- >> WORKAREAs could go either way, but it simplifies concurrency to >> file locking for native file RDDs to have them thread local. Of course >> with > > In Harbour it will works in the same way. You can also move WA between > threads. The xbase++ compatible functions dbRelease() and dbRequest() exist > in harbour. > In the future I'll add also support to clone workarea. Such cloned WA > will use common file IO handles, buffers and file lock pool. I'm also > thinking about adding pseudo exclusive mode which will be exclusive for > other applications but cloned WA will be synced internally without file > locks. > --- > > but I didn't found any other reference. > > best regards, > Lorenzo > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour > _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
