Thank you Matt. I am going to look into it right now.

Thanks,
Brian

<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>

On Tue, Mar 15, 2022 at 2:39 PM Matt Pavlovich <mattr...@gmail.com> wrote:

> I echo what Justin said about the recommending to use a STOMP or other
> protocol library for C.
>
> FWIW— There is an unmaintained c-library here--
> https://github.com/fusesource/fusemq-c <
> https://github.com/fusesource/fusemq-c> that is a C wrapper around the
> C++ library. This would need major updating to be useful.
>
> Thanks,
> Matt Pavlovich
>
> > On 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>
>
>

Reply via email to