It's probably only worth exposing for testing purposes and not much else. 

The concurrency optimizations might not be worth it. This is more of a note to keep in mind. 

Jamie Winsor
@resetexistence

> On Sep 1, 2013, at 12:38 PM, Evan Owen <notifications@github.com> wrote:
> 
> In lib/berkshelf/cached_cookbook.rb:
> 
> > @@ -1,6 +1,12 @@
> >  module Berkshelf
> >    class CachedCookbook < Ridley::Chef::Cookbook
> >      class << self
> > +
> > +      # @return [Hash]
> > +      def loaded
> > +        @loaded ||= {}
> @reset in fact, we probably shouldn't be exposing the loaded cookbooks at all, right? I'm not using CachedCookbook:: loaded anywhere right now, so the only interface should probably be from_store_path.
> 
> And as long as the internal implementation is thread-safe, it would allow us to make it asynchronous again with minimal effort. Though in my brief tests, Celluloid didn't help performance in a measurable way. I suppose the overhead of threads outweighs the small gain you get in concurrency here.
> 
> —
> Reply to this email directly or view it on GitHub.