Hello, Bill!

Bill Karwin wrote:

> I admit I am nudging toward LDAP for another reason: another suggestion
> for InterBase that I have heard from time to time is to allow IBServer
> to take user/password configuration from an operating system directory,
> instead of isc4.gdb. LDAP is often used for user directories (e.g.
> NDS).
>
> My broader vision is to allow an LDAP server to provide an
> enterprise-wide user _and_ database directory.

I do not understand why LDAP idea rised at all.
LDAP and other tools only useful to know what public resources are available.
(maybe for more tasks, but it's not sufficent).

Database server is not the same. Nobody except application developer
need to know how databases on the server are named, in what directory
they are placed, and moreover, what alias need to be used to access
these databases.

aliases for IB is only needed to hide full database paths and names.
Don't they? So, this does not mean that alias list must be published
in any way.

If some administrator wants to create published DB alias list, he can
do it right now using sockets or other tools (maybe MIDAS).
Application first will connect to alias server, then take alias,
server, database path and name, and then connect to database.
I do not see any difficulties here. And think that IB's aliases
is completely another thing to be.

--
Dmitry Kuzmenko, Epsylon Technologies.