Hi Mick,
Yes you are correct.
> A major value of a JMS broker is when there are any number of clients or
> indeed none
> (who don't need to know about each other's existence) sending to and
> receiving from a Destination.
I am trying to use it, by violating it major principle.
Thank you very m
consultpa wrote
>
> I'm getting started with Stomp and ActiveMQ coming from an MQSeries
> background. Want to use php stomp interface and see references to
> Stomp.php but cannot find it anywhere. Yes I have looked thru the doc.
> I'm must be glossing over something. A little help woul
For a small no. of such pairs, with a reasonably static existence, I would
use a Destination per pair.
I hope it's not heresy here to suggest that maybe what you need is RMI
rather than JMS. A major value of a JMS broker is when there are any number
of clients or indeed none (who don't need to kno
Hi Mickhayes,
> I think that if you draw the picture for what you have described, you will
> see that you are trying to share > a JMS Connection CX between your
> producing process (JMS client) SSX and a different consuming process > SRX
> (a different JMS Client).
> Process SS1 cannot have the t
