1st mail to the group! Wahey!

Daniel - I'm a fan of this. Makes for easy reading and as you quite rightly
say it's functional too. As for the DRIZZLE_PLUGIN or
DRIZZLE_DECLARE_PLUGIN : I'm in favour of the shorter of the two.

Cheers

Andy

On Thu, Dec 8, 2011 at 9:37 PM, Daniel Nichter <[email protected]> wrote:

> I'd like to make the Drizzle plugin names uniform.  Currently, they're not
> uniform:
>
> | FilesystemCatalog
> | Signal Handler
> | Error_message_stderr
> | Syslog
> | connection_id
> etc.
>
> That make its really difficult to systematically query D_D.MODULES and
> .PLUGINS if you want to know something about a particular module/plugin
> (and I'm sure people will want to do this eventually, e.g. to see what
> version of plugin they're using, if a plugin is loaded, etc.).
>
> So I propose making all plugin names uniform, matching [a-z_]+.  This may
> only pose a problem for DATA_DICTIONARY-CATALOG_CACHE and friends.  If so
> we can relax the pattern to [a-zA-Z_-]+.  Also, instead of
> FilesystemCatalog (camel case), filesystem_catalog, etc.
>
> If other people think this is a good idea, the next question is:
> DRIZZLE_PLUGIN or DRIZZLE_DECLARE_PLUGIN?  Why not use just one?  But which
> one?  Hingo said in another thread that DRIZZLE_DECLARE_PLUGIN is newer,
> but I prefer DRIZZLE_PLUGIN because it's shorter and forces all the
> plugin's metadata (authors, version, etc.) into its plugin.ini, and since I
> don't think we can get rid of the plugin.ini, it seems logical to me to
> centralize metadata in it.
>
> -Daniel
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to     : [email protected]
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help   : https://help.launchpad.net/ListHelp
>
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to