I had thought about this extensively, and raised the issue a couple of times in
the normal qt-interest mailing list.
I'm going to paint with a wide brush, but where we left it was the following:
1. A utility to generate a class implmentation files (cpp, h) from the service
description file (wsdl) containing QObject-derived class so that signals and
slots are used for the call and return.
2. A runtime-generated object via QMetaObject was not preferred.
3. A SOAP 1.2 w/MTOM+XOP is preferred, and about as complicated as ti will get.
(SOAP w/MIME attachments (As opposed to base-64 encoded attachments in XML (MS
XML .NET parsers has performance issues with large documents, as well as the
memory implications and more complicated streaming scenarios)
I think that's the short version.
________________________________
From: Tomasz Siekierda <[email protected]>
To: [email protected]
Sent: Saturday, August 13, 2011 9:51 AM
Subject: [Qt5-feedback] Web service functionality in Qt5
Hi,
I'm wondering, whether there are some people interested in seeing (even basic)
web service communication functionality in Qt5? I think that with Qt5 being
heavily QML (and thus, mobile) oriented, some easy way to call web methods,
without using 3rd party libs, is needed. Currently, a lot of apps do require
frequent Internet communication (to mention one use case: stock exachnge
readers) with WSes. Even a simple implementation, capable of getting the result
fast, without subclassing anything, would be nice, IMO. At the same time, it
will leave more complicated issues to well established packages, like GSOAP.
Now, to the main point: a couple of months ago I'v started developing a
project, which aim is to provide Qt devs with the ability to communicate with
web services. At that time, there was (and still is) GSOAP, but it was not made
"the Qt way", was IMO too complicated and not terribly intuitive. There also
was QSoap, which was more Qt-oriented, but AFAIK had some issues, and was not
recommended. Later on, while I was already hacking on my project, I've learned
about KDAB's KD Soap - which looks much better than any mentioned above, and is
definitely more advanced than my QWebService
(https://gitorious.org/qwebservice).
In QWebService, I have focused on making it intuitive, heavily Qt-based
(actually, there are no external dependencies. Communication is made using
QNAM, XML parsing - Qt XML module, everything is QDoc docummented). It can be
used both out-of-the-box, using generic classes, or by subclassing. An
automatic code generator is also included, it can take bot external URL, or
local file path to WSDL file. I'm currently developing it alone, but if anybody
is interested, feel invited to join me :) Most of the functionality is already
there, but there's still a lot room for improvements.
I'm not saying my solution has to make it into Qt, I'm perfectly fine to go
with any that will suit Qt developers' needs. I just want to raise the subject
here, since we still have a lot of time before Qt5 comes out, there is some
good stuff out there almost ready to be included, and, as I've said - I think
it's needed. What is your view here? Do we need it inside Qt, or are we
sticking to current necessity to use 3rd party stuff?
Cheers
sierdzio
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
