That's via the Option too, right? All the stuff in Option is appropriate for a client API, except I guess failSilently which AIUI is an implementation detail of putForExternalRead. How about using interfaces for this -- InvocationContext and InvocationContextSPI, plus InvocationContextImpl? The InvocationContext interface just exposes the getters that make sense for a client, and via getOptionOverrides() makes the Option available. If getOptionOverrides() is the only thing a client InvocationContext interface should expose, then maybe it makes more sense to change Cache so it exposes Cache.getOptionOverride() rather than getInvocationContext(). CacheSPI can expose getInvocationContext(). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052598#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...