Daniel Rail wrote:

>Hello Simon,
>
>Tuesday, September 28, 2004, 12:02:13 PM, you wrote:
>
>
>
>>The following is a list of what I would consider nice to have features when
>>hosting fb 1.5 in an isp environment. My apologies if some/all have been
>>suggested before as I'm new to the list.
>>
>>
>
>
>
>>1. Alias Manager API - I have searched but have not found anything
>>about this.
>>
>>
>
>You are right. It doesn't exists in Firebird. But, I don't know
>about Vulcan.
>
>

Vulcan has abandoned the alias mechanism in favor of a more powerful
database configuration mechanism. Database configurations can be
wildcarded with reasonably intelligent filename rewriting as well as
per-database configuration parameters. Configuration files are designed
to cascade, so an individual configuration file could cascade to a
project file cascading to a site file cascading to the distribution
configuration file. An API isn't really appropriate, though a GUI tool
to manage the suckers might be.

>
>
>>2. Ability to disable users.
>>3. Ability to assign users to databases, preferably using security.fdb.
>>
>>
>
>Points 2 and 3 are on-topic with the user management/authentication
>threads currently going on.
>
>
>
>>4. Improved logging, allow:
>> - Log failed connections.
>> - Log successful connections (user and database).
>> - log ip address for all log items
>> - change log file to delimited format for easy importing into other
>>apps
>> - Log bandwidth (in/out) by user - Maybe too much but worth asking
>>:-)
>> - Log code for easy searching of log's
>> - Maybe using security.fdb for logs (this might not be too clever in
>>long run)
>> - Daily log files instead of 1 all encompassing log file.
>>
>>
>
>
>
>
>
>>5. Option to disable non sysdba use of server api functions.
>>
>>
>
>This would actually be a nice feature and fits within the security
>discussion.
>
>

I agree. We should make sure the security plugin API can support these
things.


[Non-text portions of this message have been removed]