Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[paho-dev] Namespace for Paho Javascript client

Ok, so Javascript doesn't really do namespacing, but the current situation where we drop an object called Messaging in the global context seems a little off, and we've had a bug against it for a while now; With 1.0.0 due out shortly it should be resolved before then. I'm proposing that we make it Paho.MQTT instead, the top level object should be a unique name and gives us scope to do other clients in the future.


Back to the top