Hi Adam,

>
> I agree it would be nice, providing it is disabled by default or there
> is some method of whitelisting which aliases are 'advertised'.
>

I agree - how they are 'advertised' is the key - we do it by prefix in
aliases.conf.

>
> With superserver, that may work, although as soon as the final
> connection to a database is closed, the server 'forgets about' the
> database. Classic server has a single process per connection, so it
> isn't even aware of those databases.
>
> I suspect that this alias resolution feature would be quite confusing
> if it at certain times did not list some databases.
>

By 'available' I didn't mean connected - rather 'advertised' - in
aliases.conf.

>
> Perhaps what is needed is some more advanced version of aliases.conf
> that is a database in its own right like aliases.fdb ;)
>
> The downside would be the overhead of opening a database
> rather than a simple text file.
>
> Maybe it is
> as simple as adding sections (similar to ini files) to the
> aliases.conf for say [private] or [public] which defines what
> subsequent some future API is allowed to return to the client.
>
> It may be worthwhile to make an enhancement request.
>

Again I agree - I guess that would depend on whether it fits with the
roadmap & the kind of work that is required - I'd like it - but don't feel
competent to comment.

Max