I see the new RabbitMQ connector followed the same API scheme as the Kafka connector. i.e., adding Rabbitmq{Consumer,Producer} for the source/sink respectively. It looks like it could have followed the MqttStreams approach instead.
@yanghua, is there a reason you chose to offer o.a.e.connectors.rabbitmq.Rabbitmq{Consumer,Producer} instead of just RabbitmqStreams? — Dale > On Mar 22, 2018, at 1:11 PM, Dale LaBossiere <dml.apa...@gmail.com> wrote: > > Hi Chris. Hopefully the background provided some useful context. But like I > said, I don’t feel strongly about some renaming if folks agree that’s the > right think to do. > > — Dale > >> On Mar 22, 2018, at 12:56 PM, Christofer Dutz <christofer.d...@c-ware.de> >> wrote: >> It was just something I had to explain every time I showed the code for the >> currently by far most interesting use-case for my plc4x pocs at the moment >> (pumping data from a PLC to a Kafka topic) . So I thought, that if I have to >> explain it every time, cause people are confused, then probably we should >> talk about making things more clear. >