Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: Plug-in architectures

by abstracts (Hermit)
on Mar 14, 2002 at 02:41 UTC ( #151582=note: print w/replies, xml ) Need Help??

in reply to Plug-in architectures


The idea seems interesting as it allows installing plugins (or modules) by simply downloading them to a specific directory (/usr/share/perl/something or ~/.perl_modules). However, I don't like the idea of scanning all tgz files in these directories at runtime as it seems to would kill startup time.

I think the application should scan plugin directories for plugin names to build a hash of available plugins. Later, when a plugin is actually needed, the xml or whatever file would be located, dependencies are checked and files are loaded. Runtime errors (or warnings) can occur if necessary.

Following this track, I think the file names could also contain an optional version number because an application may require a specific version of a plugin.

Could plugins or modules conflict with one another? If they can, then you may be on your way to a more sophesticated mechanism for implementing packaging (it might look like deb or rpm).

Dunno what others think about this and I hope I didn't miss an important point.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://151582]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (5)
As of 2016-10-26 05:38 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (336 votes). Check out past polls.