See inline...
On Fri, Jul 5, 2013 at 7:46 PM, prgtrdr <prgt...@gmail.com> wrote: > I'm a bit confused by the config for Stomp and have found seemingly > conflicting info in the documentation. Please help! > > I'm planning to have a stand-alone ActiveMQ server exposed to the public > internet running on a Windows Server 2008 r2 (URL: my.webserver.com). > There > will be several local clients running on the same machine as ActiveMQ > (Javascript in an IE9 browser, and/or C# in a separate process) and several > remote clients running either Javascript in various browsers and/or Python > scripts (stomp.py). It seems like there are two different options for > configuring ActiveMQ: > > 1. Using Stomp from a remote client browser you would use (in > conf\activemq.xml): > <transportConnector name="websocket" uri="ws://0.0.0.0:61614/> > and when you connect from the remote Stomp client, the URI is: > ws://my.webserver.com:61614/stomp This looks right when using a browser that supports websockets (most of them : ) ) > > > 2. Using Stomp locally (i.e., from the same machine as the broker): > <transportConnector name="stomp" uri="ws://0.0.0.0:61613/> > and when you connect from the local Stomp client, the URI is: > stomp://my.webserver.com:61613/ Whenever you expose the transport using ws:// you're expecting a client to use websockets. If the client wants to connect using just STOMP (not in the browser), then you would expose the transport using stomp://0.0.0.0.61613 and the client would connect to tcp://0.0.0.0:61613 and use the stomp protocol (stomp.py for example). Give it a shot and let us know how it works! > > Does this look right? Is it necessary to use ws: from the remote machine > and stomp: from the local machine? What URI would you use if you were > connecting from a remote Python script (running stomp.py)? > > Thanks in advance for any help. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Stomp-Configuration-tp4668952.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
