05.11.2015 9:44, Alex Peshkoff wrote:
> But imagine a more generic case - company X has 2 plugin modules
> containing each some plugins without source code but with same
> registration names. That plugins should be loaded in parallel. Renaming
> a file with plugin module is trivial, but how to refe
On 11/04/2015 01:07 PM, Adriano dos Santos Fernandes wrote:
> On 31/10/2015 11:41, Alex Peshkoff wrote:
>> On 10/30/2015 08:53 PM, Adriano dos Santos Fernandes wrote:
>>> On 30/10/2015 11:57, Alex Peshkoff wrote:
On 10/30/2015 04:00 PM, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 1
04.11.2015 12:07, Adriano dos Santos Fernandes wrote:
> Looks like plugins are loaded on-demand, and the problems come from that.
>
> IMO all plugins should be loaded.
I'm against such nonsense, sorry. Or i not understand you (it happens)
Regards,
Vlad
--
On 31/10/2015 11:41, Alex Peshkoff wrote:
> On 10/30/2015 08:53 PM, Adriano dos Santos Fernandes wrote:
>> On 30/10/2015 11:57, Alex Peshkoff wrote:
>>> On 10/30/2015 04:00 PM, Adriano dos Santos Fernandes wrote:
On 30/10/2015 10:57, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 10:5
On 10/30/2015 08:53 PM, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 11:57, Alex Peshkoff wrote:
>> On 10/30/2015 04:00 PM, Adriano dos Santos Fernandes wrote:
>>> On 30/10/2015 10:57, Adriano dos Santos Fernandes wrote:
On 30/10/2015 10:53, Dimitry Sibiryakov wrote:
> 30.10.2015 13
On 30/10/2015 11:57, Alex Peshkoff wrote:
> On 10/30/2015 04:00 PM, Adriano dos Santos Fernandes wrote:
>> On 30/10/2015 10:57, Adriano dos Santos Fernandes wrote:
>>> On 30/10/2015 10:53, Dimitry Sibiryakov wrote:
30.10.2015 13:35, Adriano dos Santos Fernandes wrote:
> I said that externa
On 10/30/2015 04:00 PM, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 10:57, Adriano dos Santos Fernandes wrote:
>> On 30/10/2015 10:53, Dimitry Sibiryakov wrote:
>>> 30.10.2015 13:35, Adriano dos Santos Fernandes wrote:
I said that external plugins are not loaded without editing Firebir
30.10.2015 13:57, Adriano dos Santos Fernandes wrote:
> What's the [Firebird] type of this plugin?
Forget it. I'm sorry, I forgot that Avalerion don't use Firebird's plugin
loading system.
PS: Firebird has no replication plugins.
--
WBR, SD.
--
On 30/10/2015 10:57, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 10:53, Dimitry Sibiryakov wrote:
>> 30.10.2015 13:35, Adriano dos Santos Fernandes wrote:
>>> I said that external plugins are not loaded without editing Firebird
>>> supplied configuration files.
>>Avalerion's CDC plugin
On 30/10/2015 10:53, Dimitry Sibiryakov wrote:
> 30.10.2015 13:35, Adriano dos Santos Fernandes wrote:
>> I said that external plugins are not loaded without editing Firebird
>> supplied configuration files.
>Avalerion's CDC plugin is loaded perfectly well without editing
> plugins.conf.
>
Wha
30.10.2015 13:35, Adriano dos Santos Fernandes wrote:
> I said that external plugins are not loaded without editing Firebird
> supplied configuration files.
Avalerion's CDC plugin is loaded perfectly well without editing plugins.conf.
--
WBR, SD.
--
On 30/10/2015 10:29, Dimitry Sibiryakov wrote:
> 30.10.2015 13:25, Alex Peshkoff wrote:
>> But Adriano is talking about a place for information that currently must
>> go into plugins.conf and we try to find a solution that does not require
>> editing plugins.conf when such info must be set on plugi
30.10.2015 13:25, Alex Peshkoff wrote:
> But Adriano is talking about a place for information that currently must
> go into plugins.conf and we try to find a solution that does not require
> editing plugins.conf when such info must be set on plugin install.
AFAIU, Adriano said that config from
On 10/30/2015 02:33 PM, Dimitry Sibiryakov wrote:
> 30.10.2015 12:28, Alex Peshkoff wrote:
>> I can agree with it. Just to make it explicit - a method of locating
>> file with_internal_ configuration values by name of plugin with
>> extension changed to .conf must be dropped in that case. Is it OK
30.10.2015 12:24, Alex Peshkoff wrote:
> You did not pay attention to
>> >There are 2 types of plugin configuration
> As a minimum them must be separated one from another
Frankly, I see no point in "two types of plugin configuration".
--
WBR, SD.
--
30.10.2015 12:28, Alex Peshkoff wrote:
> I can agree with it. Just to make it explicit - a method of locating
> file with_internal_ configuration values by name of plugin with
> extension changed to .conf must be dropped in that case. Is it OK?
To make explicit:
a) Every plugin has PluginName
On 10/30/2015 02:02 PM, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 06:59, Alex Peshkoff wrote:
>> On 10/29/2015 06:53 PM, Adriano dos Santos Fernandes wrote:
>>> On 29/10/2015 13:42, Alex Peshkoff wrote:
On 10/29/2015 06:26 PM, Adriano dos Santos Fernandes wrote:
> Hi!
>
>
On 10/30/2015 01:14 PM, Dimitry Sibiryakov wrote:
> 30.10.2015 11:07, Alex Peshkoff wrote:
>> When writing include file one anyway must have Plugin-Name and {} pair
>> in it
> Why? If config file has the same name as plugin module and is in the same
> place, why to
> make users additional trou
On 30/10/2015 06:59, Alex Peshkoff wrote:
> On 10/29/2015 06:53 PM, Adriano dos Santos Fernandes wrote:
>> On 29/10/2015 13:42, Alex Peshkoff wrote:
>>> On 10/29/2015 06:26 PM, Adriano dos Santos Fernandes wrote:
Hi!
Initial implementation of external engines didn't needed to edit
>>
30.10.2015 11:07, Alex Peshkoff wrote:
> When writing include file one anyway must have Plugin-Name and {} pair
> in it
Why? If config file has the same name as plugin module and is in the same
place, why to
make users additional troubles with its format?
--
WBR, SD.
---
On 10/30/2015 12:46 PM, Dimitry Sibiryakov wrote:
> 30.10.2015 9:59, Alex Peshkoff wrote:
>> Not at all - if we decide to keep .conf files for plugins in
>> plugins/conf (or where-ever else) and use wildcard include in plugins.conf:
>>
>> include $(DIR_PLUGINS)/conf/*.conf
>>
>> Do you want me to d
30.10.2015 9:59, Alex Peshkoff wrote:
> Not at all - if we decide to keep .conf files for plugins in
> plugins/conf (or where-ever else) and use wildcard include in plugins.conf:
>
> include $(DIR_PLUGINS)/conf/*.conf
>
> Do you want me to do changes?
Before doing that consider the case when tw
On 10/29/2015 06:53 PM, Adriano dos Santos Fernandes wrote:
> On 29/10/2015 13:42, Alex Peshkoff wrote:
>> On 10/29/2015 06:26 PM, Adriano dos Santos Fernandes wrote:
>>> Hi!
>>>
>>> Initial implementation of external engines didn't needed to edit
>>> Firebird configuration files. You could just dr
On 29/10/2015 13:42, Alex Peshkoff wrote:
> On 10/29/2015 06:26 PM, Adriano dos Santos Fernandes wrote:
>> Hi!
>>
>> Initial implementation of external engines didn't needed to edit
>> Firebird configuration files. You could just drop files in the plugins
>> directory and they worked.
>>
>> Now tha
On 10/29/2015 06:26 PM, Adriano dos Santos Fernandes wrote:
> Hi!
>
> Initial implementation of external engines didn't needed to edit
> Firebird configuration files. You could just drop files in the plugins
> directory and they worked.
>
> Now that seems broken. File plugins/udr_engine.conf seems
29.10.2015 16:26, Adriano dos Santos Fernandes wrote:
> Now that seems broken. File plugins/udr_engine.conf seems to be
> completely unused.
>
> There is a plugins.conf file needing every plugin to be configured there.
It works fine for my plugin. Something should be broken in udr_engine itself
Hi!
Initial implementation of external engines didn't needed to edit
Firebird configuration files. You could just drop files in the plugins
directory and they worked.
Now that seems broken. File plugins/udr_engine.conf seems to be
completely unused.
There is a plugins.conf file needing every plu
27 matches
Mail list logo
