Both ActiveMQ brokers (i.e. "Classic" and Artemis) support industry standard protocols like AMQP, STOMP, MQTT, etc. Clients for these protocols are available on a wide variety of platforms in numerous different languages. These clients are not developed or maintained by the ActiveMQ community. They are 100% independent.
However, each broker also has a "native" protocol which it supports. ActiveMQ "Classic" supports OpenWire and ActiveMQ Artemis supports "core" as well as OpenWire. The ActiveMQ community *does* maintain clients for these protocols, although these are mainly supported in Java. Technically speaking there are OpenWire client implementations for both C++ [1] and .NET [2], but neither of those will fit your needs. My recommendation is to find a C client which supports either AMQP or STOMP. Justin [1] https://activemq.apache.org/components/cms/ [2] https://activemq.apache.org/components/nms/ On Tue, Mar 15, 2022 at 10:53 AM Brian Alizadeh <rastm...@gmail.com> wrote: > Dear Sir/Madam, > > We have a product that uses Sun Message Queue. Our plan is to change the > Sun Message Queue with other products. > > I found out about ActiveMQ and it seems to be a good replacement for Sun > Message Queue. I tried to find the ActiveMQ C-API but couldn't find it yet. > > I found this link: > https://activemq.apache.org/cross-language-clients > > It mentioned "defunct" in front of the C. but in the table, the second row > is C/C++ and it mentioned STOMP in the protocol section. So it is kinda > confusing as to whether ActiveMQ has a C api or not? > > I know ActiveMQ has an API in many other languages, but unfortunately we > have to use C-API in our product. > > So my question is that if ActiveMQ has a C-API that we can use to replace > the Sun Message Queue? > > Thanks, > Brian Aliz > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon > > > Virus-free. > www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
