| Subject | Re: [ib-support] Network-Some Q's |
|---|---|
| Author | Helen Borrie |
| Post date | 2002-08-06T10:25:03Z |
At 09:03 AM 06-08-02 +0000, you wrote:
clients are using the NetBEUI ("Windows networking") protocol.
designed to be workstations to an NT host, and/or to participate as peers
in a file-serving environment.
Win9x/ME machines can be Firebird servers in a TCP/IP network. Generally,
don't do it except on a very small, closed network. This OS provides
absolutely no security protection.
protocol is remote: applications do not touch the database directly at
all. The client library provides the packaging on behalf of the
application and provides communication with at database - not file -
level. The path has to be a physical local path ONLY.
it's not recommended in applications since the application cannot tell if
the connection gets terminated abnormally. Play it safe and use a local
loopback connection to connect a local console user to the DB.
It's not wise to plan to use the server machine as a workstation in a
production environment. The application will starve the server of
resources. The database server should be a completely dedicated machine.
A favourite cheap route is to run your database under Linux on a machine
that has become useless, resource-wise for Windows applications. You can
pick up some brilliant P2's for peanuts at computer fairs and such. HDDs
and memory are cheap as chips and Firebird will go like blazes when it has
a 200 MHz CPU all to itself.
heLen
All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
______________________________________________________________________
>1)I read in a post that you cannot serve firebird from a Win98/MEIt's true that you cannot serve Firebird from a Win9x/ME server host when
>machine. Is this true?
clients are using the NetBEUI ("Windows networking") protocol.
>Why is this?These platforms do not have server capability in this protocol. They are
designed to be workstations to an NT host, and/or to participate as peers
in a file-serving environment.
Win9x/ME machines can be Firebird servers in a TCP/IP network. Generally,
don't do it except on a very small, closed network. This OS provides
absolutely no security protection.
>2)When setting up the connection, I understand the DatabaseNameYou CANNOT use shares to point to the database file. The connection
>property needs to be server:drive+path\dbName
>If the share name is simply \data, do I still need d:\data?
>Is DatabaseName the correct property to use here?
protocol is remote: applications do not touch the database directly at
all. The client library provides the packaging on behalf of the
application and provides communication with at database - not file -
level. The path has to be a physical local path ONLY.
>3) Can a particular machine (poss. Win98) which hosts the db to theYes, one local connection can be made (the command line tools do it) but
>clients also have someone on the machine accessing the same db? (I
>know this is not recommended, but is it possible) Does it just come
>down to the Protocol property?
it's not recommended in applications since the application cannot tell if
the connection gets terminated abnormally. Play it safe and use a local
loopback connection to connect a local console user to the DB.
It's not wise to plan to use the server machine as a workstation in a
production environment. The application will starve the server of
resources. The database server should be a completely dedicated machine.
A favourite cheap route is to run your database under Linux on a machine
that has become useless, resource-wise for Windows applications. You can
pick up some brilliant P2's for peanuts at computer fairs and such. HDDs
and memory are cheap as chips and Firebird will go like blazes when it has
a 200 MHz CPU all to itself.
heLen
All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
______________________________________________________________________