|
|
|
good chemistry is complicated, and a little bit messy -LW |
|
| PerlMonks |
Comment on |
| ( #3333=superdoc: print w/ replies, xml ) | Need Help?? |
|
If you do this, then I would suggest making the plug-in
architecture itself pluggable. :-)
Note that many people have implemented plug-in type structures where they store the code in a database table. The same can be done with dbms as well. Abigail has the amazing module described here which can be used to pull down plugins from the network. I see nothing wrong with being able to mix and match at will... (Not that I would see a need for this. My needs are met by existing solutions. I just think this would be kind of neat to see.) In reply to Re (tilly) 1: Plug-in architectures
by tilly
|
|