plugin pooling?

View: New views
3 Messages — Rating Filter:   Alert me  

plugin pooling?

by bobpaige :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Looking at this page (http://www.jspwiki.org/wiki/PluginDevelopment) it
appears plugins are re-instantiated for every call as opposed to pooled or
even treated as singletons.

Any change this is going to change in the future? It could impact how some
of my in-house plugins work (using member variables vs. thread locals,
etc.).

Just checking :)

--
Bobman

Re: plugin pooling?

by Harry Metske :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Bob,

as far as I know, there are currently no plans to change this behavior.

Harry


2009/5/26 Bob Paige <bobpaige@...>

> Looking at this page (http://www.jspwiki.org/wiki/PluginDevelopment) it
> appears plugins are re-instantiated for every call as opposed to pooled or
> even treated as singletons.
>
> Any change this is going to change in the future? It could impact how some
> of my in-house plugins work (using member variables vs. thread locals,
> etc.).
>
> Just checking :)
>
> --
> Bobman
>

Re: plugin pooling?

by Janne Jalkanen :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Yup, plugins are treated as very lightweight objects that can be  
instantiated at will.

/janne

On 26 May 2009, at 19:56, Harry Metske wrote:

> Bob,
>
> as far as I know, there are currently no plans to change this  
> behavior.
>
> Harry
>
>
> 2009/5/26 Bob Paige <bobpaige@...>
>
>> Looking at this page (http://www.jspwiki.org/wiki/ 
>> PluginDevelopment) it
>> appears plugins are re-instantiated for every call as opposed to  
>> pooled or
>> even treated as singletons.
>>
>> Any change this is going to change in the future? It could impact  
>> how some
>> of my in-house plugins work (using member variables vs. thread  
>> locals,
>> etc.).
>>
>> Just checking :)
>>
>> --
>> Bobman
>>