Re[2]: [Firebird-devel] Using Fbembed as a client for IB5.6

[Nando D. <na...@de...>]

Mike,

MN> If the user is
MN> notified that "This version of fbembed not only contains the local server,
MN> it also has the capability to connect to other Firebird servers" that's
MN> cool, but in all honesty I'd rather try to keep this functionality in
MN> fbclient.dll where it (again, IMHO) belongs.

MN> Perhaps the y-valve compiled into fbembed.dll could look for fbclient.dll
MN> and if present use that one for remote connections (implies if it's not
MN> present, no remote connections are allowed)? IIRC there is (or at least was)
MN> some DLL loading code in it, though it looked for DLLs with names like AAAA,
MN> BBBB, or something like that.

Looks like a good compromise to me, and architecturally it certainly
makes the most sense. Let's see what others think.

>> I'd dare to propose that fbembed should be able to be used as a client
>> even for a local server (that is, connecting to databases through the
>> local protocol), e.g. a way should be found to specify in the
>> connection string whethere it's an "embedded" connection or one to be
>> forwarded.

MN> Once it has been given the capability to do remote connections, it can
MN> connect to whatever machines it likes using whatever protocol it supports.

Not if it takes all local connections strings for itself. A way to
clearly identify an embedded connection strings would be needed to be
able to differentiate (e.g. embedded:c:\localdatabase.fdb vs
c:\localdatabase.fdb).

Ciao
-- 
Nando                            mailto:na...@de...