|Subject||Re: [Firebird-Architect] External engines - metadata|
> We can have a generic API wrapper that can be used for anyAt the moment entry points are passed to the call of the plugin
> language/component set that works with fbclient.dll.
> This wrapper may define how to attach with current database based on the
> connection string, as Jaybird do.
> So in your component, you just change library name to the wrapper library.
explicitly. The components don't have such capability, so when they load
the wrapper, the wrapper must _somehow_ discover the entry points. TLS?