Gabriel Roldan ha scritto:
> thaaat's what I call a satisfactory answer :)
>
> Rini, see how FeatureTypeCache is used in WFSConfiguration.configureContext
>
> As Justin suggested, the same way you can register a new instance of,
> say, IdLookUp in GMLConfiguration.configureContext and have
> AbstractFeatureTypeBinding take an extra constructor argument of type
> IdLookUp (if my understanding is correct the picocontainer will take
> care of passing over the constructor argument as long as it's registered
> by GMLConfiguration)
>
> Then IdLookUp might be something like:
> class IdLookUp{
> ...
> boolean idExists(String gmlId){...}
> void add(String gmlId){...}
> }
>
> May you have time to do that so we fix the perf penalty?
Sounding in just for a quick check. Is the IdLookup necessary even
for simple features? How much will it cost in terms of performance
having it always on?
I was thinking that maybe in case of simple features the need is
not there and a dummy implementation could just always return
false to idExists and avoid both the search and memory consumption
overhead?
Then again, I don't fully understand the use case. It's just that
yesterday was chatting with a user that was asking why GML3 output
was so much slower than GML2 (on 1.7.x) and this seems to make it
worse from that pov.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
