Hi everyone,
I've opened an issue [1] to change the uri syntax of camel-infinispan
so that it will be similar to the other cache implementations we have
in camel (hazelcast, ehcache, jcache). As additional benefit it would
make it easy to perform auto configuration of the component in
spring-boot
+1 from my side. It makes sense. --Andrea Cosentino
--Apache Camel PMC MemberApache Karaf
CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter:
@oscerd2Github: oscerd
On Wednesday, April 5, 2017 9:47 AM, Luca Burgazzoli
wrote:
Hi ev
+1
Yeah better to have it be like the other components.
On Wed, Apr 5, 2017 at 9:47 AM, Luca Burgazzoli wrote:
> Hi everyone,
>
> I've opened an issue [1] to change the uri syntax of camel-infinispan
> so that it will be similar to the other cache implementations we have
> in camel (hazelcast,
+1
I've found local caches very useful in multiple scenarios.
OT:
I was also thinking to standardize caches in order to create a sort of
short-circuit mechanism, e.g. to avoid overloading external systems with
repeated queries. Something like...
```
from("xxx")
.cache().on("${header.yyy}").ttl(
+1 for the cache dsl
:)
---
Luca Burgazzoli
On Wed, Apr 5, 2017 at 11:12 AM, Nicola Ferraro wrote:
> +1
> I've found local caches very useful in multiple scenarios.
>
>
>
> OT:
> I was also thinking to standardize caches in order to create a sort of
> short-circuit mechanism, e.g. to avoid ove
