Hi,
I haven't check details of the recent xHarbour modifications but ChangeLog
and short look at .diff suggests that the same effect can be reached by
adding support for above virtual file handles and implementing dedicated
for Harbour trivial file server so using existing DBF* RDDs Harbour user
can simply make:
use netdb:some.host:port:file ...
instead of:
use file ...
and the effect will be exactly the same.
I've looked to new xHarbour remote RDD code, and I do not understand why
it is called NETRDD. It should be called NETFILE ar something. It is not
related to RDD, this new code tries to change Samba file server
functionality. hb_file*() functions is changed by hb_fileNet*(). I
imagine NETRDD in another way.
This approach can also be useful, but it would be nice to have NETFILE
support for all file operations like FOPEN(), FREAD(), FWRITE() (and for
C level file API also). Though, I still no not know why Samba is bad.
The sad part of the story is that Miguel continues development in his
copy-paste way. dbf1net.c is clone of dbf1.c, redbfcdx1.c is clone of
rmdbfcdx1.c, redbffpt1.c is clone of dbffpt1.c, etc. I guess he could do
all this in a simple way
#define hb_file*(...) hb_fileNet*(...)
#include "original_file.c"
but he cloned.
I'm a little surprised that Miguel is thinking about server making
server side closed source or commercial. Maybe it can fit xHarbour.com
model, but I will not buy it for sure :)
The last not clear part is one more IP library. I know it's a problem of
Harbour, and this part could be changed, but I do not see this new
NETRDD very useful anyway. Przemek, I guess you know multi-platform
socket compatibility issues the best, and you mentioned you are working
on socket functions a few days ago. I hope you'll be able to share your
implementation in the nearest future. I trust you socket interface and
have only one wish for it: I prefer more correct/clear implementation
that trying to be compatible with any of existing socket libraries.
ps. I still plan to work on real remote RDDs for Harbour but I do not know
when I'll find time for it and I do not know if I release it as open
source project
The last few words of this sentence is the sad part. But I guess you
have the reason for this. Thank You for your great contribution.
Regards,
Mindaugas
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
