>> BTW, when a plugin fails like this, can't perl trap the error so that it >> doesn't take the whole application down? Can the plugin API have some >> kind of error handling to trap problems in plugins? > >This has been discussed a few days/weeks(?) ago. Short answer: no, the >current slimserver api can't do this. > >One problem is that plugins in slimserver don't run in a protected area >like eg. the java applet sandbox, but can call anything, or even install >hooks to be called at certain events. > I haven't looked into the integration between slimserver and plugins. I had heard that there was a plugin API, so I assumed everything went through the interface, so I thought that protection could be inserted into this to catch errors.
It would seem that if slimserver were to call any defined concrete function in a plugin (such as initialise/shutdown methods), it should protect the call. If the plugins install hooks to be called at certain events within the slimserver code, then perhaps the plugins should be forced to register event handlers through some interface that a slimserver API provides that also protects against fatal errors being propagated into the slimserver core. I plan to (at some point) have a look into installing subversion and look at plugin development, just out of curiosity. I haven't done much perl programming (some simple html parsing and a bit of fun with perl golf http://terje2.perlgolf.org/~pgas/score.pl?func=front, where the idea to to achieve a task in the minimum set of characters possible) and I'd like to learn more. Phil _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
