|Re: [paho-dev] On Paho's opinionated URI validation|
both "" and "/" as valid paths be accepted? What about a patchAm I missing something? Would a patch that makes Paho treatpretty easy to see how a user may provide either and expect the same result.tcp://127.0.0.1:1883 and tcp://127.0.0.1:1883/ are technically two different URI's but it's* Why won't Paho accept tcp://127.0.0.1:1883 but not tcp://127.0.0.1:1883/ (with a trailing slash)* Why is there no standard mqtt:// scheme? This is very inconvenient for e.g. PaaS service providers that provide URI's that developers should use.This raises two questions:code that does it:stand out as odd usability issues.I generally find Paho Java a pretty nice library but a couple of thingsI maintain Machine Head  and work on a project that provides(RabbitMQ).
applications with URI's to connect to an MQTT capable broker
One of them is URI validation that Paho performs. Here's the exact
that makes "mqtt" an alias for "tcp" and "mqtts" an alias for "ssl"?
Just to make it clear: both will not introduce any breaking changes.
paho-dev mailing list
Back to the top