I may be okay with it continuing to be deprecated, the same functionality
is available via DataUtility methods (if a developer needs to "adapt" their
content) with the added advantage of being able to choose between direct
list use, spatial performance or sorted (like memory datastore).
I guess I would like a clear story on how developers use Memory DataStore
...
--
Jody
--
Jody Garnett
On 23 January 2015 at 12:24, Torben Barsballe <[email protected]>
wrote:
> This is completely nonfunctional codewise, but when I was updating
> MemoryDataStore to use ContentDataStore instead of AbstractDataStore, I
> forgot to remove the @Deprecated from MemoryDataStore.
>
> Fixed here: https://github.com/geotools/geotools/pull/702
>
> Torben
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> GeoTools-Devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
