Details
-
Task
-
Resolution: Fixed
-
P3: Somewhat important
-
None
-
None
Description
With the new continuation support in QFuture, it should be easy to transparently support QFuture return types in WebChannel. Method invocations from the client side are asynchronous anyway, so for the client it makes no difference if the return value of a method is sent from the continuation of a QFuture or server-side-synchronously directly after a method call.
Attachments
| For Gerrit Dashboard: QTBUG-92903 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 359127,3 | Add QFutureInterfaceBase::get() to retrieve internals of QFuture | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 359129,6 | QMetaType: Support converting any QFuture<T> to QFuture<void> | dev | qt/qtbase | Status: MERGED | -1 | 0 |
| 365956,6 | Transparently handle QFuture<T> method return types | dev | qt/qtwebchannel | Status: MERGED | +2 | 0 |