| Re: [hono-dev] Hono JMS adapter |
|
Hi,
as already said in the chat with Dejan and Dominik, we already decided (during the meeting) that Hono will be fully AMQP based so the related API as well. As specification, JMS isn't related to AMQP (they are on different abstraction layers) even if we have a JMS client which uses AMQP as underlying protocol but in order to adhere the specification introduces some limitations. I don't think that it could be a good idea to introduce such limitations in Hono. So I agree on handling JMS compatibility with an adapter but leaving Hono API more AMQP oriented. Regards, Paolo Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor From: dejanb@xxxxxxxxxxxx Date: Thu, 23 Jun 2016 14:44:43 +0200 To: hono-dev@xxxxxxxxxxx Subject: [hono-dev] Hono JMS adapter Hi,
I’ve been chatting with Dominik a bit on IRC about request-reply patterns in JMS and the issues that will impose on the Hono API. It struck me at the moment that we’ve been influencing a lot of the API lately with the limits of JMS API and clients we have available. It seems to me that it might be a better long term solution to keep Hono API focused on the things it needs to do and natural to AMQP protocol, and deal with these JMS compatibilities issues in an adapter of some kind (in a similar fashion we’ll deal with other protocols over time). What do you guys think about this? It’d be good to have this sorted before we go further in changing the API. _______________________________________________ hono-dev mailing list hono-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/hono-dev |