Hello
What you could probably do in this case is to embed a broker either in the
producer or the consumer, so the one of them communicates with the broker
using the VM transport. The other one will can still talk to the embedded
broker using the TCP transport.
However, if you have the producer or the consumer on the same machine as the
broker, the overhead of TCP is probably minimal.
The embedded broker approach will work fine if both the producer and the
consumer are Java, or if one of them is Java and the other is C++. If both
your producer and consumer are C++, you will have to have a separate broker,
because the C++ library is only a client library (i.e., there's no easy way
to embed a broker inside your C++ program, and there isn't something like a
VM transport).
Hope that helps.
Regards,
Albert
----- Original Message -----
From: "Motl" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, October 10, 2007 8:05 PM
Subject: activemq: direct tcp connection
Hi,
If I need direct TCP connection for performance reasons, but still want to
use JMS api, is it possible to do that in some way?
Sorry for unclear question, but in some cases I only need 1 producer and 1
consumer and I want direct TCP connection between them.
If I could do it within activemq, less code will require changes on the
caller side.
I am asking about both java and c++ implementations.
Thank you.
--
View this message in context:
http://www.nabble.com/activemq%3A-direct-tcp-connection-tf4602430s2354.html#a13141078
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
