Hi, I'd like to discuss another point about restoring fdb. As it used to be and it is now, the path DB (libarma_path_db.gz) is obtained from the local cache and written back both to the cache and as a RK taxi file. I think this is not correct. Its management should be homogeneous with that of smalldb. That is, the taxi file should be the "master" and the local cache should be just that: a local copy of the one in the RK.
Once we realize that the management of the Path DB must be RK-centered, we should also acknowlwdge that files may go into the RK from different computers (this is how I've noticed that the Path DB is obtained from the cache, rather than the RK). Accordingly, if we want to use the Path DB to allow copying the RK files back to the dirs they came from when uploaded, I think the info in the filedb should include the name of the computer. Of course, the contents of the path DB can be useful for other things, including a new lkarmafs; so while the origin path (and computer) is a good default for the contents for each fid, we shold take into account that application programs (riocp, lkarmafs, etc.) may want to directly access and change the value of this pathname property. So some policy is needed regarding contents and format. Best, EV. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-karma-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-karma-devel
