(to toad@,  cc devl@  and infinity0@ )

On Tue, Jul 28, 2009 at 9:28 PM, Mike Bush<mpbush at gmail.com> wrote:
> Yeah we are both working on freenet/plugin-Library-Staging.
> I haven't pushed the FredPluginAPI thing to freenet, it's in
> platy/fred-staging. Yesterday some problems with the way it is
> supposed to work was pointed out, that the plugins each have their own
> classloader so they cant share classes. Maybe we could also put that
> in the API thing to share classloaders, Infinity0's been looking into
> it too.

hmmm....
The classloader problem is uneasy, it can't be solved without
a full blown plugin dependency framework -- which I don't
think you can complete in the GSoC timeframe.

I think you should do what WoT / Freetalk is using  - use FredPluginFCP.
In which data are serialize before sending between plugins and
no classes are shared between plugins.

> The bliki-doclet thing is something infinity0 added I don't think he
> spoke to toad about it, I'll ask. I think the GoogleCollections is to
> do with that too but I'm not sure.

@toad:
did you look at the bliki-doclet dependency ?

> Thanks for the patch I hadn't thought of that but knew it needed something.
>
> I only just looked recently at the bug reports for spider/librarian
> and most of the bugs are things which were discussed in my proposal
> originally and I was planning to do. I'm going to work through the
> bugs while we work out how to do the API thing and I work out how to
> make the search and ui i did earlier work with the new index format.

So the classloader is the only major blocker, right?

> Thanks for the comments
> Mike
>
>
> 2009/7/28 Daniel Cheng <j16sdiz+freenet at gmail.com>:
>> Sorry for yet-another-email, but i have missed something:
>>
>>
>> (4) I can see a google-collections ?reference in the build.xml
>> ? ?Are you / infinity0 going to use it?
>> ? ? If not, please remove it.
>> ? ? If yes, you may want to work with toad and get it into
>> freenet-ext.jar so it won't be duplicated.
>>
>>>
>>> Regards,
>>> Daniel Cheng
>>>
>>
>

Reply via email to