|Re: [paho-dev] Python MQTT native vs. as binding|
I'm pretty experienced using SWIG. I commonly use it to wrap C++11
libraries so that I can debug interactively with Python, and then
write test and diagnostics apps in Python as well. But I deliver the
final apps in C++, so I've never looked into the performance or
efficiency of the SWIG wrappers.|
I can help out with SWIG if anyone thinks we might want to go this way.
But first I would ask two questions:
(1) In a networked application is the Python client layer the real bottleneck?
(2) In a high performance application would you use Python for the app?
I don't mean to insult anyone's personal love for one language or another, but it would be interesting to devise a performance test for the different language client libraries so that we can make a development-time vs performance decision for individual projects.
On 12/01/2017 08:55 AM, Ian Craggs wrote: