----- Original Message ----
> From: Iván Todorovich <[email protected]>
> To: [email protected]
> Sent: Thu, May 26, 2011 4:47:49 PM
> Subject: [Qt5-feedback] Improved QFuture
>
> QFuture should be improved to support custom subclasses. Nowadays
> asynchronous calls are *very* important, and it should be easier to
> make them. QFuture should be the standard result of every async method
> and, in time, Qt should make use of that standard, for instance in
> async http request (QNAM), QtMobility, sockets, an ideal QtSQL with
> async support, etc.
+1
In general I find QtConcurrent weak at best, and reverted to only using the
QRunnable class
(dunno if it is even part of Conc, now when I think about it...).
MihailNaydenov
> _______________________________________________
> 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
