* Volker Fervers <mailing at edv-fervers.de> [2006-07-13 09:31:45]: > Hello! > > I'm trying to understand how to handle plugins for .7. > > The .url file "myplug.jar.url" with the reference to the jar file for the > plugin class contains something like: > http://localhost:8889/freenet:SSK at > some_SSK.../myplug-7/myplug.jar?forcedownload > > If I enter > http://www.example.com/some_path/myplug.jar.url > on the plugin page of FProxy I can load my plugin successfully while using > http://localhost:8889/freenet:SSK at some_SSK.../myplug-7/myplug.jar.url > results in a PluginNotFound error in the log. > > I checked the inserts of the myplug-7 freesite manually and they are ok. From > the code I cannnot see, why using FProxy instead of 'normal' HTTP shouldn't > work. (Timout = 5 * 100ms?) > > My aim was to publish even the plugins anonymously. Or doesn't that make > sense > to you? > > GV
In fact you shouldn't do it that way :) Ask the user to download the .jar (http://localhost:8889/freenet:SSK at some_SSK.../myplug-7/myplug.jar) and to put it on his hard drive. Then ask him to put "*@file:///path/to/plugin/myplug.jar" in the plugin-loading box. The purpose of using http is to be running "always latest", ... Moreover the node hasn't fully started when we are loading plugins on bootup, that's probably why it doesn't/wouldn't work anyway. NextGen$ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20060713/e565601f/attachment.pgp>
