Subject | Registry usage on Windows |
---|---|
Author | Emil Totev |
Post date | 2008-02-13T16:00:18Z |
Hi
I've been trying to understand how Firebird 2 is using the registry.
So far I think I've found out the following:
-- The Server (super or classic) DOES NOT use the registry entry for
anything
-- The Embedded engine DOES NOT use the registry key for anything
-- The fbclient.dll reads the 'DefaultInstance' key in order to locate
firebird.msg and nothing more
-- Some of the server tools use the 'DefaultInstance' key to locate
the fbclient.dll in the bin subdirectory of the firebird root.
-- Applications are expected to read and enumerate the keys in order
to locate the fblient.dll of the instance they will work against.
If this is correct, then also
-- the client dll has no way of telling to which instance it belongs
and would always read the 'DefaultInstance' entry, making different
versions of the client library on the same machine use the same
(default) firebird.msg.
-- same applies to tools trying to locate the client dll - they always
load the default
I hope I am wrong and someone tells me how.
Thanks
Emil
I've been trying to understand how Firebird 2 is using the registry.
So far I think I've found out the following:
-- The Server (super or classic) DOES NOT use the registry entry for
anything
-- The Embedded engine DOES NOT use the registry key for anything
-- The fbclient.dll reads the 'DefaultInstance' key in order to locate
firebird.msg and nothing more
-- Some of the server tools use the 'DefaultInstance' key to locate
the fbclient.dll in the bin subdirectory of the firebird root.
-- Applications are expected to read and enumerate the keys in order
to locate the fblient.dll of the instance they will work against.
If this is correct, then also
-- the client dll has no way of telling to which instance it belongs
and would always read the 'DefaultInstance' entry, making different
versions of the client library on the same machine use the same
(default) firebird.msg.
-- same applies to tools trying to locate the client dll - they always
load the default
I hope I am wrong and someone tells me how.
Thanks
Emil