[
https://issues.apache.org/jira/browse/CAMEL-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979832#action_12979832
]
Dan Checkoway commented on CAMEL-3480:
--------------------------------------
@Richard, on the consumer side it's fairly specific to Kestrel, since it polls
a queue -- a concept that memcached proper doesn't support per se. On the
producer side, however, it could easily be adapted to become an "out only"
endpoint that would write key/value pairs to memcached.
For that matter, a consumer could be written so that it periodically "polls"
memcached for a given key being present. When found, it could process an
Exchange and delete the value from the cache. I'm not sure if this is as
realistic of a use case as the "out only" producer, but I guess it's doable.
I looked at the Cache component, which does similar things...but that has the
luxury of being tied into an in-JVM instance of ehcache. The notion of polling
memcached for a value to appear isn't as sophisticated as being able to detect
"events" like the Cache component can with ADD/UPDATE/DELETE/DELETEALL event
handlers.
Anyway, that's my brain dump on that idea for now. Holler if you think there's
demand for a general memcached component.
> New component: Kestrel
> ----------------------
>
> Key: CAMEL-3480
> URL: https://issues.apache.org/jira/browse/CAMEL-3480
> Project: Camel
> Issue Type: New Feature
> Reporter: Dan Checkoway
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: CAMEL-3480-20110110-full.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I'm proposing that some adapted open-source code for producing to/consuming
> from Kestrel be added as an official Camel component. Currently the code
> lives here: https://github.com/dcheckoway/camel-kestrel
> Please assign this to me if you'd like me to own this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
