camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4400) Consumer Endpoint for AWS SNS Service
Date Sun, 12 Jul 2015 07:36:04 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623698#comment-14623698
] 

Claus Ibsen commented on CAMEL-4400:
------------------------------------

Thanks [~markford] - that is an endless discussion. 

I still think its valid to have a consumer, and can help get the code into Camel. But maybe
people are not using AWS as much anymore, now that there is so many other cloud services around.
So we could also just close this ticket if so.

Any thoughts?

> Consumer Endpoint for AWS SNS Service
> -------------------------------------
>
>                 Key: CAMEL-4400
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4400
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>            Reporter: Kai Wähner
>             Fix For: Future
>
>
> Contrary to S3 and SQS, Camel only offers a producer endpoint for this AWS service. You
can only create topics and send messages via Camel. The reason is simple: Camel already offers
endpoints for consuming these messages: HTTP, Email and SQS are already available.
> But there is a huge tradeoff: A consumer cannot subscribe to topics using Camel. The
AWS Management Console has to be used.
> The original contribution of camel-sns contained a consumer for easily configuring and
consuming the data from the topic. This was not included in the release.
> The SNS consumer should be added, because otherwise Camel is missing a core feature of
the AWS SNS service.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message