Re: [hono-dev] Why we shouldn't correlate messages based on message ID

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [hono-dev] Why we shouldn't correlate messages based on message ID

From: Gordon Sim <gsim@xxxxxxxxxx>
Date: Mon, 27 Jun 2016 11:01:46 +0100
Delivered-to: hono-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/hono-dev>
List-help: <mailto:hono-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/hono-dev>, <mailto:hono-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/hono-dev>, <mailto:hono-dev-request@eclipse.org?subject=unsubscribe>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company Registration No. 3798903, Directors: Michael Cunningham, Michael O'Neill, Eric Shander
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1

On 27/06/16 10:59, Hudalla Kai (INST/ESY1) wrote:

Is there any
particular property of the Dispatch Router or any of Red Hat's message
brokers that would prevent us from using the correlation ID pattern?

No.

References:
- [hono-dev] Why we shouldn't correlate messages based on message ID
  - From: Hudalla Kai (INST/ESY1)

Prev by Date: [hono-dev] Why we shouldn't correlate messages based on message ID
Next by Date: Re: [hono-dev] Why we shouldn't correlate messages based on message ID
Previous by thread: [hono-dev] Why we shouldn't correlate messages based on message ID
Next by thread: Re: [hono-dev] Why we shouldn't correlate messages based on message ID
Index(es):
- Date
- Thread

Breadcrumbs