Yes, a single broker can support many clients, so once you have one (that will be online whenever any of the clients will want to connect to it), you don't have to have one for the clients. There are sometimes reasons that people would want to do that (primarily because it decouples the client from the standalone broker if the standalone broker is sometimes unavailable, or if the network link to the standalone broker is high-latency), but it's absolutely not required (or typical), and nothing you've described sounds like you would have those needs.
The CMS libraries are absolutely an option for a C++ client; they'd be the first option I considered for C++ code with an ActiveMQ broker, and I'd pick them over the AMQP approach you originally described if you can make them work with Yocto. And yes, in all languages, if you're a client application, you simply include the ActiveMQ libraries and run; there's no additional installation required and no other processes that need to be running before you can connect to the standalone broker. Tim On Sun, Jan 31, 2016 at 4:11 AM, motic <motic.m...@gmail.com> wrote: > Hi Robbie, > > Thanks for taking the time to reply! > As I mentioned, I'm new to this subject, therefore I have no idea as to the > AMQP architecture. > One more question if I may.. > > As far as I understand it, I need to have only one Broker and it will be > accessed by several clients - is that right ? I mean that once I have the > ActiveMQ broker running on my Application serever - I dont need to have > another broker on my Device driver side - just a client. > > The reason I'm asking is because I found some C APIs online - so in case > they are compatible with AMQP - all i need to do is to compile them to a > library and use it on my device driver side, no need for any additional > installtions - right ? > > In addition, I encountered the CMS API ( http://activemq.apache.org/cms) > <http://activemq.apache.org/cms/> - can I consider it as another option > for a C++ client ? > > Thanks again. > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-and-AMQP-Qpid-RabbitMQ-tp4706562p4706696.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
