Thank you, Nate Do you have any example in SSL/STOMP/Ruby ?
Thanks a lot for your time. On Thu, 2007-11-01 at 09:36 -0400, Nathan Mittler wrote: > Our discussion has been specifically about the C++ client, ActiveMQ-CPP. > The wire format (OpenWire, Stomp) is a layer on top of the transport (tcp). > It is done this way so that you can use any wire format with any transport. > ActiveMQ-CPP does not yet support an SSL transport, therefore it is > unavailable for use with any wire format. > > If you're using Java, you certainly can use SSL with Stomp or OpenWire. See > http://activemq.apache.org/ssl-transport-reference.html. > > Regards, > Nate > > On 11/1/07, Marcos Alvares <[EMAIL PROTECTED]> wrote: > > > > In activemq, have no way to build a stomp client using ssl connection? > > > > Have you any activemq clients using ssl examples? > > > > thank you > > > > On Wed, 2007-10-31 at 17:28 -0400, Timothy Bish wrote: > > > Stomp provides an interoperable wire format so that any of the available > > > Stomp Clients can communicate with any Stomp Message Broker to provide > > > easy and widespread messaging interop among languages, platforms and > > > brokers. Stomp does not have inherent support for the transport, ie. > > > TCP, UDP, SSL, etc. > > > > > > So no, you can't use the stomp wireformat support in ActiveMQ-CPP to > > > communicate over SSL. > > > > > > Regards > > > Tim. > > > > > > mrh wrote: > > > > The truth is, I don't know much about Stomp at all, but I thought I > > read > > > > somewhere that as a protocol it supported SSL? I could very well be > > making > > > > that up though, lol. But if it does, I wondered if might be possible > > to > > > > specify stomp as the protocol and use it to make an SSL connection. I > > > > apologize in advance for my ignorance of the library... still trying > > to > > > > understand everything. > > > > > > > > Thanks again, > > > > mrh > > > > > > > > > > > > Tim Bish wrote: > > > > > > > >> No definite time line at the moment. I'm not sure how stomp could be > > an > > > >> alternative to SSL could you elaborate? > > > >> > > > >> > > > > > > > > > > > > > > >