On 8/7/20 2:08 PM, Christopher Pisz wrote:
Yes, I did a Google search.
It yields code examples or javascript libs. I need a built client that
connects with a different protocol, so I can quickly test that the server
will allow clients to connect at all.
You can try the ActiveMQ JMS client library which uses a TCP or SSL
socket connection and uses the Openwire protocol, or you could use Qpid
JMS which speaks AMQP 1.0 and can connect via TCP, SSL or Websockets to
test configured WS and WSS endpoints.
http://qpid.apache.org/components/jms/index.html
There's an older StompJMS library that isn't maintained but should still
work to test connections
https://github.com/fusesource/stompjms
On Fri, Aug 7, 2020 at 2:05 PM Justin Bertram <jbert...@apache.org> wrote:
There are lots of STOMP clients for various platforms written in various
programming languages many of which do not use websockets. What exactly do
you need? Did you try doing an Internet search?
Justin
On Fri, Aug 7, 2020 at 1:00 PM Christopher Pisz <christopherp...@gmail.com
wrote:
So I installed ActiveMQ on a remote machine this morning.
Created the default broker.
Attempted to connect with the client I wrote using websockets.
Connection is refused.
I then tried running the examples/protocols/stomp/stomp-websockets
example
Attempted to connect with the client I write using websockets
Connection is refused.
Attempted to connect using the index.html from my machine rather than the
remote(as localhost there)
Connection refused.
I don't know what to do.
Is there another premade client I can connect with that doesn't use
websockets, so I can at least narrow it down and see if the server works
at
all?
Any other suggestions?
On Wed, Jul 29, 2020 at 5:21 PM Wayne Robinson <wayne.robin...@gmail.com
wrote:
Websockets don’t use the same-origin policies that other AJAX requests
do.
You will most likely need to serve them via TLS to prevent browser
errors,
but there’s nothing special you need to do to setup CORS.
On Thu, 30 Jul 2020 at 1:47 am, Christopher Pisz <
christopherp...@gmail.com>
wrote:
I have a process that runs in California that wants to talk to a
process
in
New York, using Stomp over Websockets.
Also note that my process is not a web app, but I implemented a stomp
over
websocket client in C++, in order to connect things up to my backend.
Maybe
this was or wasn't a good idea. So, I want my client to talk to the
server
and subscribe, where their client pushed messages.
I was implementing my own server when I saw that ApacheMQ supported
Stomp
over Websockets. So, I started reading the docs.
It says:
One thing worth noting is that web sockets (just as Ajax) implements
?
the same origin policy, so you can access only brokers running on
the >
same host as the web application running the client.
Is this a limitation of the server or the web client?
With that limitation, if I understand right, the server is not going
to
accept websocket connections from a client, of any kind, that is not
on
the
same machine?
I am not sure I see the point of that...
If that is indeed its meaning, then how do I get around it in order
to
implement my scenario?
--
Tim Bish
