There is a .NET client library for ActiveMQ 5.x that uses the OpenWire
protocol, which means that it should work for Artemis as well. That's
probably the easiest option. But you could also use STOMP or an AMQP
library if you had a reason to want to use those protocols instead of
OpenWire.
Tim
On
How is this different from your previous question?
On Oct 25, 2017 1:24 AM, "bhattacharyyasom"
wrote:
> Hello,
>
> I have the following scenario that i want to address using queuing. I am
> not
> very sure if this is feasible though.
> So today i have a .NET rest services developed on the WebAPI
Thank you very much for quelling my doubts whether this can be worked at all
!
Yes i have a very cursory idea of how the messaging works. So i will read up
on protocols and their differences.
I have one question though what is the recommended protocol for use with
.Net ?
--
Sent from: http://act
Hello,
I have the following scenario that i want to address using queuing. I am not
very sure if this is feasible though.
So today i have a .NET rest services developed on the WebAPI interface that
receives JSON messages and calls different database procedures with that
parsed data.
Recently i ca
This is a really broad question that would probably be better answered via
a consulting service of some kind. That said, I'll attempt a concise
answer.
I think the first thing you'd want to do is figure out which message broker
you are going to use - ActiveMQ 5.x or ActiveMQ Artemis. Involved in
Hello,
I have the following scenario that i want to address using queuing. I am not
very sure if this is feasible though.
So today i have a .NET rest services developed on the WebAPI interface that
receives JSON messages and calls different database procedures with that
parsed data.
Recently i ca
