Community
Participate
Working Groups
- MQTTClient is available on github (https://github.com/ckrey/MQTT-Client-Framework) 29 Watchers 129 Stars 51 Forks 121 Commits 6 Contributors - Distributed via cocoapods (https://cocoapods.org/pods/MQTTClient) 6048 Downloads 140 Installs - MQTTClient is a full MQTT 3.1.1 implementation - Implements TLS including Client Certificates. Optionally based on Keychain or pinned certificates - MQTTClient is now fully backward API compatible with MqttSDK - MQTTClient implements persistence based on CoreData - Implements off-line queueing - Implements in and out flow-control and and message throttling/limiting - MQTTClient offers an additional Blocks based API now as suggested by Jeff Mesnil (https://dev.eclipse.org/mhonarc/lists/paho-dev/msg01305.html) - MQTTClient is fully useable from SWIFT - MQTTClient is released for iOS, OSX, and tvOS - Extensive test cases based on XCode/XCTestCase interoperability coverage exceptions 11 out of 22 = 50% statements 74 out of 79 = 93%
Hi Christoph. Thanks very much for submitting this. I will submit the question to the Eclipse legal team about what is now allowed by Apple's T&Cs first, then if the answer is generally approving we can move ahead with details of the contribution. I see there are 6 contributors. If we can go ahead with the contribution then I think that if they have all signed the Eclipse CLA this will make it as easy as possible.
*** Bug 402265 has been marked as a duplicate of this bug. ***
Hi Christoph. I was hoping that the license issues we previously had with adding xCode artifacts into an Eclipse repository might be lessened somewhat. After a discussion with the Eclipse legal team it seems that the situation has not changed since the previous contribution. However I would very much like to have your client in Paho, and if you wanted, for you to be part of the Paho team. As we are now making Github the location for our repositories, and I believe that Github is the main location for your code, then I'm thinking that we could have the source code in the Eclipse Github repository, and anything that couldn't be hosted there, could reside in your repository. This way we could we could have a good build and distribution story for users. How does that sound? If you would like to go ahead, then the next step would be to identify the percentage of code written by each contributor, and each will need an Eclipse CLA (https://eclipse.org/legal/CLA.php). Please ask if you have any questions. Thanks, and apologies for the delay.
Unfortunately, this is now out of date.
