camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Checkoway (JIRA)" <>
Subject [jira] Commented: (CAMEL-3480) New component: Kestrel
Date Mon, 10 Jan 2011 22:55:47 GMT


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

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:
>             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:
> 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.

View raw message