Hi all,
It seems to me that installing Koha plugins is easy enough. Each Starman process will load the plugin into memory because it hasn't seen it before. However, if you're updating/upgrading a plugin, each Starman process has already loaded it, so it won't know that it needs to reload it. I think most of us work around this at the moment either by restarting Plack or just letting the Starman workers die and be replaced by new ones that use the updated code. But that doesn't seem optimal for an environment that allows user plugins. That said, https://advent.plackperl.org/2009/12/day-4-reloading-applications.html and https://metacpan.org/pod/Module::Reload have a few points on how reloading code in a persistent process is a good way to get bugs. I recall Kyle saying Wordpress was his inspiration for the plugins. I'm curious how Wordpress handles plugin upgrades. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
