camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Manes (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10267) Create a Caffeine component
Date Wed, 21 Jun 2017 20:57:00 GMT


Ben Manes commented on CAMEL-10267:

Thanks for this! :-)

I haven't had the pleasure to use Camel so I'm unsure about the workflow experience. The features
you may (or may not) want to add in a future iteration are,
* RemovalListener provides an async notification, e.g. to close a resource like a socket.
* CacheWriter provides a sync notification for create/update/delete, e.g. to update a second
resource atomically (perhaps a file system cache)
* Fixed and variable expiration (Expiry). The latter is when the external resource defines
policy, e.g. an http expire header, so each entry can have a different duration.

Fyi, some behavior can be performed asynchronously (e.g. removal listener, async cache). That
can be annoying in unit tests so you can provide a same-thread executor. Not sure if that
would be useful to expose, handled automagically by your test kit, not an issue, ...

> Create a Caffeine component
> ---------------------------
>                 Key: CAMEL-10267
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Minor
>             Fix For: Future
> It would be great to have a Caffeine component:

This message was sent by Atlassian JIRA

View raw message