This idea/notion is much too Windows centered.

The idea which has/had been proposed is to allow for alias mappings (ex.
"Sean = d:\developement\database\sean.gdb") to be registered on the
server such that clients could access simply via a server name and alias
name combination (ie. server_name:alias_name or my_server:sean).

This approach could be incorporated (retrofitted) into the server
without breaking any of the existing code/applications.


Sean

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


So the map S: is on the client not a server running Interbase? If so I
see
what you mean and cool. If not my original concern stands.

Cheers
Adam

----- Original Message -----
From: "Bill King" <ungod@...>
To: <IB-Architect@egroups.com>
Sent: Wednesday, August 09, 2000 12:05 AM
Subject: RE: [IB-Architect] Re: Is it _really_ necessary to expose the
location of the database file?


> 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
>
>
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com
>
>
>
>




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