Re: [Firebird-devel] COM for Plugins

2014-08-11 Thread Dimitry Sibiryakov
11.08.2014 10:38, Alex Peshkoff wrote: > Next, COM means UTF16 (at least on windows). Do we want to change our > favorite UTF8 to UTF16 on every call? We decided that we do not. > > And last issue. IUnknown alone is far not a full COM, at least > automation is needed. I do not know an easy way to h

Re: [Firebird-devel] COM for Plugins

2014-08-11 Thread Alex Peshkoff
On 08/09/14 01:30, Jim Starkey wrote: > Isn't COM a natural technology for plugins? Load a module, lookup the query > interface interface, then probe for known interfaces. If one is found, it > identifies both the formal interface and, by implication, the type of plugin. > > By definition, COM

Re: [Firebird-devel] COM for Plugins

2014-08-09 Thread Dimitry Sibiryakov
09.08.2014 19:29, marius adrian popa wrote: > I vote with Jim on this , if we reinvent com at least we can use it as > it should , I would use xpcom from mozilla Mozilla? That slow and hungry-for-RAM browser?.. I would be very sceptical about anything from them. -- WBR, SD.

Re: [Firebird-devel] COM for Plugins

2014-08-09 Thread marius adrian popa
I vote with Jim on this , if we reinvent com at least we can use it as it should , I would use xpcom from mozilla https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM On Sat, Aug 9, 2014 at 12:30 AM, Jim Starkey wrote: > Isn't COM a natural technology for plugins? Load a module, lookup th

[Firebird-devel] COM for Plugins

2014-08-08 Thread Jim Starkey
Isn't COM a natural technology for plugins? Load a module, lookup the query interface interface, then probe for known interfaces. If one is found, it identifies both the formal interface and, by implication, the type of plugin. By definition, COM interfaces are immutable, so there is not quest