After testing and comparing with mosquitto (http://mosquitto.org) using
mosquitto's python client the behavior is still different (and not very
usable, sadly)
Connecting with keepalive=0 results in the _client_ disconnecting
immediately from the server (either mosquitto or activemq). So setting ke
ActiveMQ (5.7 snapshot) and MQTT: connection times out while still connected
to a topic for receiving
I'm using mosquitto's python client to connect to an mqtt topic. When using
the mosquitto broker,
all works (but that broker doesn't allow me to plug in authentication to my
database, so it's no r
Got it working by overriding message send (As the Stomp protocol had similar
behaviour i guess the behaviour mentioned above is intentional):
===
class UpoAuthenticationBroker(next: Broker, admin_user: String, admin_pw:
String
When using mqtt as transport i try to allow only certain users to publish to
certain topics.
However, when using mqtt (python's mosquitto client) to publish to a topic,
the producerinfo in the addProducer method of the broker filter doesn't hold
a destination (it's always null), making it impossib
