Hello, Bill!

Bill Karwin wrote:

> in the server access method. That is, one could CONNECT "$alias" and
> the client gds32.dll looks up $alias and finds it maps to
> "linuxserver:/usr/local/data/blah/blah/blah.gdb".

Why client gds32.dll need to know where alias maps and even real database name???
I thought that database name only used to say SERVER what database must
be open for client. So, client is not interested how database is named.
He needs to connect to it. Will it be alias name or full path and gdb name -
doesn't matter.

> Alternately, the server could do the mapping: in CONNECT
> "linuxserver:$alias" the ibserver daemon would look up $alias and find
> that it maps to /usr/local/data/blah/blah/blah.gdb.

I think it must be the only way to translate aliases. Do simple things :-)

> Example: gds32.dll would load aliases from ibconfig upon startup. If I
> try to connect to an alias, it first searches its cached alias list, and
> if it can't find the alias I want, it then requests resolution from the
> LDAP server. If that doesn't work, then it returns an error.

Have you seen applications that can work with different databases, and
they are not development tools? database names are almost hard-coded
in applications.
And why gds32.dll need to know alias list? For what? For hacker, sitting
somewhere and looking for interbase aliases all around the world?

--
Dmitry Kuzmenko, Epsylon Technologies.