Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-12 Thread Adriano dos Santos Fernandes
On 12/01/2016 06:31, Vlad Khorsun wrote: > 11.01.2016 16:49, Adriano dos Santos Fernandes wrote: >> Hi! >> >> In this function, seems one could not known what database needs the >> plugin. That's bad. >> >> In current engine implementation, multiple attachments has multiple >> metadata caches and p

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-12 Thread Vlad Khorsun
11.01.2016 16:49, Adriano dos Santos Fernandes wrote: > Hi! > > In this function, seems one could not known what database needs the > plugin. That's bad. > > In current engine implementation, multiple attachments has multiple > metadata caches and plugins instances. > > But Java External Engine plu

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-12 Thread alex
11.01.2016 20:32, Adriano dos Santos Fernandes пишет: > On 11/01/2016 15:13, alex wrote: >> 11.01.2016 19:00, Adriano dos Santos Fernandes пишет: >>> On 11/01/2016 13:31, alex wrote: 11.01.2016 17:49, Adriano dos Santos Fernandes пишет: > Hi! > > In this function, seems one could

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 18:47, Adriano dos Santos Fernandes wrote: > If you keep talking completely out of context things in this thread, I > have nothing to discuss with you. If you don't want to hear ways to solve your problem different from what you fixed on - ok, but in this case whole thread is just

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 15:40, Dimitry Sibiryakov wrote: > 11.01.2016 18:35, Adriano dos Santos Fernandes wrote: >> Who wants and why wants to limit a plugin (in this discussion) to a >> single database? >Nothing prevent you from configuring the plugin for several databases as > soon as > CORE-4482 is

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 18:35, Adriano dos Santos Fernandes wrote: > Who wants and why wants to limit a plugin (in this discussion) to a > single database? Nothing prevent you from configuring the plugin for several databases as soon as CORE-4482 is implemented. -- WBR, SD. -

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 15:25, Dimitry Sibiryakov wrote: > 11.01.2016 18:13, alex wrote: >>> Yes, getDatabaseName in IPluginConfig may work. >> Even better to use database ID from lock manager - it's guaranteed to be >> free of any file naming issues when deciding is it same db or not. >Just configure yo

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 15:13, alex wrote: > > 11.01.2016 19:00, Adriano dos Santos Fernandes пишет: >> On 11/01/2016 13:31, alex wrote: >>> 11.01.2016 17:49, Adriano dos Santos Fernandes пишет: Hi! In this function, seems one could not known what database needs the plugin. That's bad. >>

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 18:13, alex wrote: >> Yes, getDatabaseName in IPluginConfig may work. > Even better to use database ID from lock manager - it's guaranteed to be > free of any file naming issues when deciding is it same db or not. Just configure your plugin in databases.conf, as it is done for key ho

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 18:11, Adriano dos Santos Fernandes wrote: > I do want to share the IExternalEngine between attachments in super classic. Then it is enough to return a singleton from factory. But it is not the way classic is supposed to work. -- WBR, SD. -

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 15:49, Adriano dos Santos Fernandes wrote: > But Java External Engine plugin loads classes stored in the database, > and they should be loaded in a classloader per database, not per > attachment, which would be heavy. If your Java External Engine can query database for classes, it ca

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread alex
11.01.2016 19:00, Adriano dos Santos Fernandes пишет: > On 11/01/2016 13:31, alex wrote: >> 11.01.2016 17:49, Adriano dos Santos Fernandes пишет: >>> Hi! >>> >>> In this function, seems one could not known what database needs the >>> plugin. That's bad. >>> >>> In current engine implementation, m

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 15:05, Dimitry Sibiryakov wrote: > 11.01.2016 15:49, Adriano dos Santos Fernandes wrote: >> But Java External Engine plugin loads classes stored in the database, >> and they should be loaded in a classloader per database, not per >> attachment, which would be heavy. >If your Java

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 17:25, Adriano dos Santos Fernandes wrote: > If you need to share things, you need to share things, not half-things. A lot of things are already shared. Are you sure that it is not enough? Do you have a feature request from somebody? >>In any case, if you want to share the sam

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 14:06, Dimitry Sibiryakov wrote: > 11.01.2016 16:57, Adriano dos Santos Fernandes wrote: >> IPluginBase (base of IExternalEngine) is, and that's what I want to share. >Are you sure that sharing it is a good idea? It means that methods of the > same plugin > object will be called

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 16:57, Adriano dos Santos Fernandes wrote: > IPluginBase (base of IExternalEngine) is, and that's what I want to share. Are you sure that sharing it is a good idea? It means that methods of the same plugin object will be called from multiple threads in parallel. Programming of such

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 13:31, alex wrote: > > 11.01.2016 17:49, Adriano dos Santos Fernandes пишет: >> Hi! >> >> In this function, seems one could not known what database needs the >> plugin. That's bad. >> >> In current engine implementation, multiple attachments has multiple >> metadata caches and plugins

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 13:37, Dimitry Sibiryakov wrote: > 11.01.2016 16:28, Adriano dos Santos Fernandes wrote: >> It's dumb to have: >> - MT capable (super client) engine with non working Java plugin >> (spanning a classloader per attachment) >> - Non-MT capable (super) engine with working Java plugin (spa

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 16:28, Adriano dos Santos Fernandes wrote: > It's dumb to have: > - MT capable (super client) engine with non working Java plugin > (spanning a classloader per attachment) > - Non-MT capable (super) engine with working Java plugin (spanning a > classloader per database) If we are tal

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread alex
11.01.2016 17:49, Adriano dos Santos Fernandes пишет: > Hi! > > In this function, seems one could not known what database needs the > plugin. That's bad. > > In current engine implementation, multiple attachments has multiple > metadata caches and plugins instances. > > But Java External Engine p

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
On 11/01/2016 12:59, Dimitry Sibiryakov wrote: > 11.01.2016 15:49, Adriano dos Santos Fernandes wrote: >> In current engine implementation, multiple attachments has multiple >> metadata caches and plugins instances. >What do you mean? At least database encryption plugin is loaded only once > f

Re: [Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Dimitry Sibiryakov
11.01.2016 15:49, Adriano dos Santos Fernandes wrote: > In current engine implementation, multiple attachments has multiple > metadata caches and plugins instances. What do you mean? At least database encryption plugin is loaded only once for a database (in superserver). -- WBR, SD. ---

[Firebird-devel] PluginFactory::createPlugin - identify the database

2016-01-11 Thread Adriano dos Santos Fernandes
Hi! In this function, seems one could not known what database needs the plugin. That's bad. In current engine implementation, multiple attachments has multiple metadata caches and plugins instances. But Java External Engine plugin loads classes stored in the database, and they should be loaded i

Re: [Firebird-devel] PluginFactory

2015-11-04 Thread Vlad Khorsun
04.11.2015 18:26, Dimitry Sibiryakov wrote: > Hello, All. > > Plugin factory can produce only one type of plugin? If my module provides > several > plugins, I have to create separate factories for each one? > Yes on both questions. Regards, Vlad --

[Firebird-devel] PluginFactory

2015-11-04 Thread Dimitry Sibiryakov
Hello, All. Plugin factory can produce only one type of plugin? If my module provides several plugins, I have to create separate factories for each one? -- WBR, SD. -- Firebird-Devel mailing list, web interfa