First of all, I'm not sure what flag you're talking about here. In the context of Infinispan, when we talk about flags, we normally refer to http://docs.jboss.org/infinispan/4.1/apidocs/org/infinispan/context/Flag.html
I assume you're refering to some kind of configuration option rather than a flag as per the definition above.
It'll be interesting to hear other people's thoughts but personally, I don't like the idea you suggest cos it moves away from the peer-to-peer architecture where all peers are equals to each other within a cluster, all of them having the same config.
For an scenario where you wanna separate state providers from state consumers, I'd create two clusters, one with providers and the other with consumers and you could connect between them via RemoteCacheStore+HotRod.
I was referring to the '
fetchInMemoryState' attribute of the 'stateRetrieval' element in the Infinispan configuration.
Perhaps a better way to say it is that we would like to see 2 attributes (generateInMemoryState / retrieveInMemoryState) on this element. It may be that we have a unique use case. In particular, the state transfer creates a coupling between nodes that we would like to limit.
Interesting about 2 clusters. I remember you mentioned that in a previous discussion on Hot Rod usage.