Re: [infinispan-dev] InboundInvocationHandlerImpl optimization

> > The problem is, you can inject a NAMED_CACHE component into another > NAMED_CACHE component, or a GLOBAL component into a NAMED_CACHE > one, but never a NAMED_CACHE component into a GLOBAL component. > (Guess why!) What about having an IIH instance for each cache(scope == NAMED_CACHE), each keeping a field references to Configuration, Cache, CommandsFactory and ResponseGenmerator. The transport would look up the appropriate IIH from a map, so we would reduce the number of lookups at one. Looking at IIH itself it rather looks quite cache-based, as all its methods have a cache name param.