On Sun, 2009-06-14 at 14:38 -0700, Nascent wrote:
> Tim,
>
> Thanks for the reply. The tutorial looks great. I have a few more questions
> though.
>
> Specifically, I am trying to use topic://ActiveMQ.Advisory.TempQueue but
> there doesn't seem to be any msg properties that I can leverage and I h
On Sun, 2009-06-14 at 14:38 -0700, Nascent wrote:
> Tim,
>
> Thanks for the reply. The tutorial looks great. I have a few more questions
> though.
>
> Specifically, I am trying to use topic://ActiveMQ.Advisory.TempQueue but
> there doesn't seem to be any msg properties that I can leverage and I h
cout << "Property: " << *itr << " = " <<
p_message->getStringProperty(*itr) << endl;
}
catch (...)
{
cout << "Property: " << *itr << " = " <<
p_message->getIntProperty(*itr) << endl;
}
}
}
--
View this message in context:
http://www.nabble.com/ActiveMQ-CPP-and-Advisory-messages-tp23983516p24026003.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On Thu, 2009-06-11 at 08:26 -0700, Nascent wrote:
> Scenario:
> I have a consumer written in C++ that uses ActiveMQ-CPP to communicate with
> ActiveMQ. It implements a callback interface where a client can request
> on-change updates for data points. The consumer then does a response message
> to
ually only interested
in a handful of them. So it seems inefficient to me to have all these data
point updates going to a topic where less than 5% of them may actually be
consumed.
Thanks in advance!
--
View this message in context:
http://www.nabble.com/ActiveMQ-CPP-and-Advisory-messages-tp2398351
