Avgustin Marinov

It seems like something that we could use. In our case we get batch of change events from the gateways that we pass to ditto (through hono) using a hono...

If you approve removal of "unauthenticated mode" I could implement it.

What is the idea here? AFAIU CloudEvents defines contract between event producer and consumers via context attributes, e.g. source/id, time, content type, subject,. Hono is an intermediary (in terms of...

External producers are perfect match for use cases like sensors producing events and (higher level) device that communicates with the backend. However, concept is applicable to Hono, I suppose. Hono...

could you assign this issue to me? I'd like to try to provide support for local development mode

in MqttPublishTestBase there are few things that could be improved/fixed: - messageHandlingCompleted.await(); should wait with certain timeout (as received.await does) - in doTestUploadMessages if sendAttempt.failed() is true and errorMessagesExpected is...

I'm not sure if the Ditto shall implement push state. This could be tricky. In order to push state, Ditto shall do that via commands (the only way Hono supports)....

I remember times when Hono was supposed (?) to have C&C in both directions (https://www.slideshare.net/dejanb/scaling-out-eclipse-hono 4th slide). Also I thing AWS IoT provides restricted support for request/response from device. Looking...

Hi all, looking at the proposals, I personally like the first approach Carsten proposed - dedicated links for request/response to backend application. I think that request/response is exactly the same...

@sophokles73 my bad, I've started to convert the request topic from the one way command topic - that's why I ended with "adapter should receive a request at `req_resp///req/${subject}`". Indeed...