Yeah I would think you would see a major performance gain anyway you are
able to bypass the SPI classpath lookup. Even doing the reflective
instantiation.
-Justin
Andrea Aime wrote:
Justin Deoliveira ha scritto:
What about instantiating specific functions directly. Perhaps with a
FilterFunctionFactory which would bypass the factory finder lookup
mechanism. This of course only works if you know which function you
need, but in this case it sounds like you do.
Agreed, but this path may be used also by others. I had time to think
about it,
and my proposal is:
* go thru the factory SPI just once, and build a map that goes from
function
names to their respective classes
* each time a function is requested by name, ask the map for the related
class,
and build an instance of the function (thus, totally bypassing the SPI
in the
normal case). These functions do have a default constructor by
default, which
is normally used by the SPI, I'm just proposing to use it in a smarter
way.
This should be fast enough. What do you think?
Cheers
Andrea
--
Justin Deoliveira
The Open Planning Project
[EMAIL PROTECTED]
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
