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

[Mike N. <ta...@al...>]

Nando Dessena asked:

> I know this is pretty much a strange setup, but I would be able to solve
many
> problems I have if I could count on this couple (Fbembed as an
> embedded server and as a client for a local or remote IB server v5.6) to
> work reliably. So, can any of the developers say why it wouldn't
> work,

You have two DLL's with the same exported names. Somehow you have to tell
your runtime what connection you want to use, in-process server or remote.
Or are you (seriously, as can be read from your post) suggesting that the
local-only (embedded) server should act as mediator for remote connections
also?

Perhaps what you need is an extra layer (your work) between Firebird and the
connection method, so your app can select local server or remote at will? To
put remote access in the local server not only creates security holes the
size of Windows 9x run by idiots clicking on any and every attachment they
get, it also muddies the waters of where what borders are.

Local in-process server, aka "fbembed" is AFAIK what it tells you to be. If
someone added remote capabilities to that DLL, all of a sudden it would have
just those remote access capabilities - i.e. it would be a security problem.

> or suggest areas to test more than others, or anyway comment on
> this one?

I suggest you do it like e.g. IBPP, dynamically load the DLL(s) and
GetProcAddress for the entry points. Else you wouldn't know what enrty point
went to server/client and ... Well, I think you can imagine the resulting
SEGV's would get messy. :-)

> Of course I plan to use dialect 1 exclusively, for now.

How would that be obvious? Personally I use nothing but dialect 3, and I
don't see a reason to hang on to anything older unless forced to.

/Mike