Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] MQTT C Shared Library Names

There are plenty of examples of longer library names on my system:

and you hardly ever have to type them in, so a longer name doesn't seem to be a problem to me.  In fact, in common with some other names, we could add a dash:


We probably don't need the v3 part, although I quite like it.  If there were ever a v4 then that could have a v4 suffix.  I'm thinking that the OASIS standard behaviour would be obtained with the same library using a flag in the connect options.


On 31/10/13 14:47, Andy Piper wrote:
I actually think maintaining the whole "paho" is important here so people have a chance of finding us from a Google search based on filename. I wonder if we need the "v3" part though?

On Thu, Oct 31, 2013 at 2:22 PM, luja <luja@xxxxxxxxxxxxxxx> wrote:
Hi all,

good idea, but keep it short,

keep it short, omit vovels like hebrews do :-)



On 10/31/2013 3:08 PM, Ian Craggs wrote:
> Hi All,
> currently the shared library names are libmqttv3 plus suffixes:
> c - synchronous, non-SSL
> cs - synchronous, SSL
> a - asynchronous, non-SSL
> as - asynchronous, SSL
> On Windows, they are mqttv3c.dll ...
> I was thinking that they should have paho in the names, for "brand"
> identification.  If they do end up in Linux distributions, or
> otherwise distributed, this may be necessary to avoid clashes in any
> case.
> So...
> libpahomqttv3c
> and
> pahomqttv3c.dll
> ?
> Thoughts?
> Ian
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx

paho-dev mailing list

Andy Piper | Kingston upon Thames, London (UK)
blog:   |   skype: andypiperuk
twitter: @andypiper  |  images:

paho-dev mailing list

Back to the top