Re: [Firebird-devel] Providers, yvalve, external engines and object lifecycle

[Adriano d. S. F. <adr...@gm...>]

On 24-03-2011 05:33, Vlad Khorsun wrote:
>>>> How it could be done ? How YValve knows about *provider's* factories ?
>>>> It's yvalve who instantiates plugins.
>>>
>>> Really ? I thought it is PluginManger, who instantiates plugins.
>>
>> I recall an agreement here that PluginManager should be a part of the y-valve, not the engine. Perhaps it's already linked this 
>> way, I haven't checked. So I believe Adriano is talking about the y-valve as a library, not as just why.cpp.
> 
>     YValve asks PluginManager to instantiate Providers. But plugns is much more wide than just
> Providers. And PluginManager is responsible to instantiate all kinds of plugins. And far not all of
> plugins need callbacks into YValve.
> 

This is because plugins creation is currently using fixed factories,
while is much better to have specific factories for specific needs.


Adriano