On Mon, Jan 2, 2012 at 2:33 PM, Andrea Aime
<andrea.a...@geo-solutions.it> wrote:
> On Mon, Jan 2, 2012 at 6:22 PM, Justin Deoliveira <jdeol...@opengeo.org>
> wrote:
>>
>> What about just having JAIInfo.jai be lazily evaluated, and have it just
>> return the JAI singleton directly. JAI.getDefaultInstance() doesn't seem to
>> be an expensive lookup at all (just returns a static singleton), so having
>> it be called continuously should not be an issue.
You mean JAIInfoImpl.getJAI(){ return JAI.getDefaultInstance();} ?
Guess it'd work. Still I'd be up to avoiding any non configuration
object as part of the configuration API. But feel free to implement it
that way or give me the go ahead and I'll do it myself. I suppose the
change should come along with the deprecation of JAIInfo.setJAI(JAI)?
Cheers,
Gabriel
>
>
> Agreed. However I guess we should setup some rule about what *Info object
> are allowed to keep state (as a field)
> and which ones cannot
>
> Cheers
> Andrea
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
