With QtNetworkAuth + QNetworkAccessManager the Firebase C++ API is not needed. So it will remove this dependency and support more platforms than the platforms supported by the Firebase libs.
Thank you for the explanation :) -- Best regards, Jesús On 2017-06-21 13:19:24+02:00 Ari Salmi wrote: Hi Jesús, Thanks for question and reaction! Qt Cloud Messaging API itself is not dependent on QtNetworkAuth, but it can be backend-solution dependent. e.g: Google firebase backend solution for Android and iOS are using firebase's c++ binaries (which app developer should give env, path when compiling) and real communication goes through those elements. Also in addition developer can create the cloud messaging server elements also with this same API, so I've included REST API interfaces (QtNetwork) to firebase and to Kaltiot.com backends. Those needs (after Qt5.6) libssl and libcrypto libraries included in to the applications (included in the example). Thanks, Ari br, Ari Ari Salmi SnowGrains<http://www.snowgrains.com> 2017-06-21 14:07 GMT+03:00 Jesus Fernandez <[email protected]<mailto:[email protected]>>: Hi Ari, Is your project dependent on QtNetworkAuth for dealing with Google API? Best regards, Jesús -- Best regards, Jesús On 2017-06-21 12:59:05+02:00 Ari Salmi wrote: Hi there, I am developing a Qt API to wrap cloud push services to mobile apps and embedded devices. This includes examples for using Google Firebase (firebase.google.com<http://firebase.google.com>) for mobile app development and similar a solution for embedded space as well (which has increasing demand). For contribution to Qt the new repository is needed. Name of the project: Qt Cloud Messaging Responsible person: Ari Salmi / SnowGrains gerrit username: snowgrains gerrit email: [email protected]<mailto:[email protected]> desired repository name: qtcloudmessaging Some background: The closest match is the Qt Mobility's QMessaging service, which more or less concentrated to SMS, mms and email services inside a (nokia) phones taking care of the contacts etc. Unfortunately that API is not expandable to other platforms and cannot be used. One aim on this is to create Qt API that wraps (and developers can do more wrappers with same API) e.g. Google firebase, or onesignal type of push messaging services - for mobile and desktop apps. More important aim is to provide similar messaging to/from iot and other embedded devices, like cars. This is the place where we are lacking the offering from the Qt point of view. One embedded backend solution that has scale able offering is Kaltiot.com. I've included it as one backend for embedded story. Thank you and best regards, Ari
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
