[paho-dev] Namespace for Paho Javascript client

[Al Stockdill-Mander <asm@xxxxxxxx>]

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; 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407372
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.
Thoughts?

Al