On 15/08/10 19:05, Luca Morandini wrote:
> On 14/08/10 23:17, Andrea Aime wrote:
>
>> Does Terracotta require the entire set of objects managed by the
>> process to be shareable?
>
> No, you can specify a subset of objects to share. I specified the
> org.geoserver.config.impl.GeoServerImpl.catalog one, which may be too wide: I
> may
> try a narrower one, which means I shall dig deeper in the GS/GT code... groan
> !
I analysed the dependencies amongst classes, and the result were not truly
encouraging: for instance, there are about 867 classes depending on WeakHashSet
(a
lot of them within the catalog: LayerInfo, DataStoreInfo, etc, etc).
AFAIU, GeoTools manages its own cache, which is at odds with the whole
Terracotta
concept.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Geotools-gt2-users mailing list
Geotools-gt2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
