Jody Garnett ha scritto: > I am fine for the revolution; should however talk with Justin who put > a lot of thought into the revolution and has a proposal outlining the > marching orders for the feature collection plot.
Yeah, I was more sharing a sentiment than suggesting we do it right now... as in, I don't have a plan and a good idea of the consequences. > I would support the revolution in order to get feature collection > separate from java.util.Colleciton; if you guys really wanted to > soften the blow we could commit to the DefaultFeatureCollection class > API as representing an in memory feature collection (and replace the > current implementation with ListFeatureCollection internals). > > Aside: I am not sure about ListFeatureCollection; I suspect a HashSet > based implementation may perform better; and offer us greater > protection against duplicates. Collection 101: array lists will outperform anything else in pure collection traversal performance and memory compactness (which also reflects in better use of the CPU 1st and 2nd level caches, which improves performance). Sets are good only if you have a stringent requirement of uniqueness, otherwise current implementations are a disgrace both performance and memory consumption wise. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
