On Tue, 01 Sep 2009, Ernad Husremovic wrote: Hi,
> Hello hb community. > A few days ago, we started porting our clipper solutions to LETODB RDD. > Today I read about new Przemek great contribution: NETIO RDD. To clarify. It's not RDD but only alternative RDD IO API library so it allows to switch transport layer in all RDDs which uses hb_file*() interface. > Reading Changelog, NETIO is also good candidate for our default RDD. > Our main goal is to provide multiplatform (linux, windows) solution NETIO RDD resolves the problem with sharing database files between different OS-es so it can be usefull in such cases. > which is not vulnerable > to data corruption caused by direct file access. But here it will not help you in noticeable way. It's not client server solution for database and index file processing. They are still updated by the local station not the server so station crash may leave index not fully updated. NETIO replaces only transport layer. > In some earlier conversation, Przemek wrote: > > BTW it's not exactly client/server solution like in ADS or NETRDD if I > > finish it. > I would like to hear community comments about the optimal choice of > (opensource) RDDs in the client/server arena. For sure full server side table and index processing is much better solution. ADS and LETO are such servers. I haven't used any of them so I cannot say too much about them. ADS is commercial project with very good user opinion. LETO is opensource project but I do not know user experience about using it in larger installations. I also cannot say too much about its internals and if it's safe or not to use it with Harbour multithread programs. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
