actually no, as it forwards database requests, not accesses to the server
interbase (exactly like ibclient) would to the server machine. so the server
interbase serves the query's etc exactly like it would if you were to
connect to the server and specify a path. so no chance of corruption, as the
server interbase is serving the data, and exactly the same amount of
bandwidth, as once again, the server interbase is processing the requests
for data etc.

-----Original Message-----
From: Adam Clarke [mailto:Adam.Clarke@...]
Sent: Tuesday, 8 August 2000 11:55 PM
To: IB-Architect@egroups.com
Subject: Re: [IB-Architect] Re: Is it _really_ necessary to expose the
location of the database file?


Unfortunately this is not a very good idea in terms of network bandwidth and
(because they are related) performance. Now all file accesses from the
engine are flying across the network. You've just converted a high
performance client server database into MS Access.

IK wouldn't be surprised if this increased the chance of corruption also but
that's just a gut feeling at this stage.

Cheers
Adam

----- Original Message -----
From: "Bill King" <ungod@...>
To: <IB-Architect@egroups.com>

> you can get this functionality at the moment using windows networking.
> interbase is kind enough to detect that the file is residing on another
> machine, and redirects all requests for that database through to the
correct
> server. (i found this one out the hard way).
> so if you map \\server\servershare to s: for example. then connecting to
> s:\test.gdb will actually connect to the server's interbase server! path
> hiding.....+full security if the share is sitting on an NT box.





To unsubscribe from this group, send an email to:
IB-Architect-unsubscribe@onelist.com