On 07/03/14 13:04, Dmitry Yemanov wrote: > 03.07.2014 12:45, Alex Peshkoff wrote: > >> In databases.conf one can use only present in firebird.conf fixed set of >> parameters. >> See config.cpp for details. >> I suppose we have no problems adding replication parameters in it. > I don't think *plugin-specific* settings belong to our config.
> On 07/03/14 12:58, Dimitry Sibiryakov wrote: > > We have no problems adding parameters now (except one: I can't > predict all of them). > > But what must do third-party plugins' developers after Firebird 3 > release? Should they > > hack Firebird engine before developing their plugins? Must they > write in documentation > > "this plugin requires custom Firebird build and won't work with any > official Firebird > > releases"? > > To be precise - we may add list of replication plugins to it if we have new type of plugin. Plugin-specific parameters certainly should not go to firebird.conf or databases.conf - they should be placed into plugin's configuration. > > Ok. Is there a place where user can put database-wide parameters > and where a plugin can > get it from exactly for the database it was loaded for? No. Do you have a suggestion? ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
