On 2009.07.23., at 0:04, Przemyslaw Czerpak wrote:
On Wed, 22 Jul 2009, Itamar Lins wrote:
Hi,
The harbor will have native support net rdd for the core team ?
Because LetoDB is god product for local LAN but is very slow,
impracticable
with WAN via ADSL for exemple.
If you ask about sth like just committed to xHarbour RE* RDDs then I
do not
think it should be part of core code though it someone wants to port
it as
fully contrib extension then why not.
Not even contrib IMO. Server code wasn't even published,
there's just a Windows 32-bit server executable uploaded
to the repo with a 2 users limit.
The rest is copy paste from letodb code, existing RDDs
and file handling routines with modifications.
AFAICS low level file handling routines were replaced
with one which work through the network directly, essentially
creating a replacement for networked file system protocols,
like SMB. As such, it will have all the problems of file
server based db access. F.e. whole index handling seems to
be done through the network (not on the server side), so it
won't make indexes any more bullet proof, or substantially
reduce network traffic.
use netdb:some.host:port:file ...
instead of:
use file ...
and the effect will be exactly the same.
This would be nice.
Generally I tend to see UI client-serverization a better
alternative to remote db, as it can work much faster on
slow networks and even more centralizes app deployment
and management. Not to say that remote db wouldn't be a
great thing to have though.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
