Re: [infinispan-dev] design for cluster events (wiki page)

In terms of API, instead of having: void currentPartitionReadOnly(); void currentPartitionAvailable(boolean available); Wouldn't it make sense to UNAVAILABLE, READ_ONLY or AVAILABLE an enum (e.g. called PartitionStatus) and then have a single method like: void markPartitionAs(PartitionStatus status); Also, we also have ComponentStatus and that's used throughout the code to determine the state if the cache and components. Although not the same purpouse, there's somewhat a link, and there's already an interceptor called InvocationContextInterceptor that, amongst other things, verifies whether a cache operation can be called on the cache. It'd probably make sense that the logic in InvocationContextInterceptor WRT controlling the cache status and the new AvailabilityInterceptor would merge into one single interceptor. Cheers, On Oct 30, 2013, at 8:05 PM, Mircea Markus <mmarkus(a)redhat.com&gt; wrote: -- Galder Zamarreño galder(a)redhat.com twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org