I quite like this idea! I think we could make this transparent as when instances are added to clustered collections (like the map and the queue) that have been obtained for a specific L1. Not sure about the technical implications of it though, it might be quite some work, but not impossible for sure :-)
On 19 May 2010, at 21:12, Jim McClure wrote: > Is it possible to byte code enhance the classes in a way that does not tie > each class to a specific L1? Enhance the class so that instances of that > class can contain the L1 data but don't set that data at class load time. > Instead, set the data when an instance of the class is actually associated > with an L1. That would allow the same class to be used for objects across all > L1s. If you can do that then you can use the instrumentation agent, do > compile time instrumentation (maybe an annotation processor?), and/or use a > custom class loader. The custom class loader would be nice for integration > into containers that want to support Terracotta out of the box and remove the > need for the agent or compile time options. -- Geert Bevin Terracotta - http://www.terracotta.org _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
