Subject Re: [Firebird-Architect] External engines - metadata
Author Adriano dos Santos Fernandes
Roman Rokytskyy escreveu:
>> We can have a generic API wrapper that can be used for any
>> 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.
> At the moment entry points are passed to the call of the plugin
> explicitly. The components don't have such capability, so when they load
> the wrapper, the wrapper must _somehow_ discover the entry points. TLS?
The wrapper may be compiled (exporting API functions) within the plugin
or loaded (DLL) by the plugin.

1) engine loads plugin
2) plugin loads and setup API wrapper to call engine entry points
3) User configure Delphi component to use wrapper DLL