Since both objects that use this cache are wired by guice, we could avoid both exposing this cache public and also avoid dealing with any side effects of statically maintained state by using guice instead.
There are many other caches in jclouds that are wired via guice. Personally, I'd prefer to not have to even consider classloader (OSGi) or other side effects of shared static state and either maintain the cache local to the 2 users or shared via guice. OTOH, I don't want to be overly prescriptive, so.. above in mind, make a call :) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/164#issuecomment-25627721
