Just few weeks ago, we announced Qt Cloud Services - everything you need for scalable and powerful cloud backend. Since then, we've continuously improved the Qt Cloud Services experience and added few new features. Read more about the supported features.
After the announcement, we've received overwhelming feedback and interest towards using them; the promise of cloud seems more relevant than ever before. The success of our first service--Enginio Data Storage--has really set a new momentum for the whole Qt ecosystem. I'm happy to tell you that we got even more exciting things in the works!
As we continue our journey of improving and adding new features, we’d also love to hear what you have to say about our upcoming ideas making your Qt Cloud Services experience better.
Some of the things we’re interested in hearing about:
- What do you like most about our current service?
- Do you think the features we are planning are useful for you?
- Which client API libraries would you like to use in addition to Qt API library?
Furthermore, if you have a few moments, we’d love for you to take this survey that’ll help us to define the future of Qt Cloud Services and enhance your overall Qt experience. And don’t forget, we also encourage you to add any comments that you may have below!
Take our survey!
Thanks for supporting Qt Cloud Services. We look forward to hearing from you!
I thought I was pretty clear. We don't want your backend. We want our own back end powered by Qt, our Qt code, though a QObject-based web server. We define the objects, the signals, slots, etc.
We don't want BaaS.
Also, we wont want WebSockets. We want comet. Yeah, its not as elegant, but the firewalls sure like it better.
@Jason: Please take a look at: http://qt-project.org/wiki/...
This is a very good feedback. Thanks.
We also want support the scenario of setting up and maintaining your own backend that is powered by Qt.