You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Stephen J <st...@mclaneco.com> on 2009/01/08 17:54:01 UTC
Cometd message consumption
It appears that the cometd component will consume messages even if a browser
client is not subscribed to the channel the cometd component is providing.
Essentially any message delivered to the component before a browser client
connects is sent to never-never land.
Is this be the expected behavior, or should the cometd component wait to
consume messages until it has a connected client to send them to?
--
View this message in context: http://www.nabble.com/Cometd-message-consumption-tp21355768s22882p21355768.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Cometd message consumption
Posted by Stephen J <st...@mclaneco.com>.
I've opened a https://issues.apache.org/activemq/browse/CAMEL-1242 JIRA
ticket requesting this enhancement, although I would also welcome anyone
else's thoughts about alternate ways to handle this type of thing through
existing camel components.
dgreco wrote:
>
> Yes,
> this is the expected behavior. I wonder if it make sense to hold messages
> if the browser is not ready.
> Anyway I didn't spend so much time thinking about it, maybe you could open
> a JIRA if this is not what you would like to have.
> Regards,
> David
>
>
> Stephen J wrote:
>>
>> It appears that the cometd component will consume messages even if a
>> browser client is not subscribed to the channel the cometd component is
>> providing. Essentially any message delivered to the component before a
>> browser client connects is sent to never-never land.
>>
>> Is this be the expected behavior, or should the cometd component wait to
>> consume messages until it has a connected client to send them to?
>>
>
>
--
View this message in context: http://www.nabble.com/Cometd-message-consumption-tp21355768s22882p21375471.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Cometd message consumption
Posted by dgreco <gr...@acm.org>.
Yes,
this is the expected behavior. I wonder if it make sense to hold messages if
the browser is not ready.
Anyway I didn't spend so much time thinking about it, maybe you could open a
JIRA if this is not what you would like to have.
Regards,
David
Stephen J wrote:
>
> It appears that the cometd component will consume messages even if a
> browser client is not subscribed to the channel the cometd component is
> providing. Essentially any message delivered to the component before a
> browser client connects is sent to never-never land.
>
> Is this be the expected behavior, or should the cometd component wait to
> consume messages until it has a connected client to send them to?
>
--
View this message in context: http://www.nabble.com/Cometd-message-consumption-tp21355768s22882p21371307.html
Sent from the Camel - Users mailing list archive at Nabble.com.