> On Aug 10, 2014, at 3:51 PM, Dimitry Sibiryakov <s...@ibphoenix.com> wrote: > > 10.08.2014 20:33, Adriano dos Santos Fernandes wrote: >> It does not make any sense to write a COM-plugin that could just say, >> "hey, I'm a plugin" and do nothing. > > You seem don't understand one things about plugins: they don't need to do > anything but > respond to engine's calls. Exactly for this (and only this) purpose they > _export_ some > kind of interface. > Fortunately, this topic is not about interface they export, but about one > they can > import from the engine. They are two completely different kinds of interface.
Indeed. However, were Firebird to go down the COM path for plugins, wrapping a COM object around the engine API to pass across plugin interfaces would definitely be the way to go: functional, simple, extensible, and forward and backward compatible. > ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
