On 2 Apr 2012, at 14:02, Tristan Tarrant wrote:
I dislike the current way of configuring stores via <property>.
As part of my work for ISPN-1821 I will also introduce the ability for stores to provide
their own configuration parsers so that we can have more readable schemas.
That
would be quite nice, as the property-based approach is very error prone. Curious how
you're going to support 'dynamic' xml snippets,through some xml name spaces
perhaps?
Participating in JTA is obviously high on the desired list, and I'd also expose some
form of batching so that intelligent cache-store can colaesce operations together for
better performance.
that's a big one indeed. JTA support won't be available
for all stores, e.g. cloud cache store.
Mind detailing a bit on the batching/colaesce functionality you have in mind?
Maybe the ability to introduce some form of compression for values (if over a certain
size threshold).
I don't think that would require a API change, as this sort of
behaviour seem to be orthogonal and can be handled to a wrapper CacheStore implementation,
very much like the AsyncCache store. Might require a configuration change though. Also I
think this is a good task for an external contributor.