On segunda-feira, 9 de setembro de 2013 19:38:20, David Faure wrote: > I still think the best solution is: > QtCore: QAbstractJob, and later QProcessJob and QThreadJob > QtNetwork: QNetworkRequestJob (wrapping QNetworkReply) > QtDBus: (later) QDBusCallJob (wrapping QDBusPendingCallWatcher) > > The latter is another reason why a QtJobs library wouldn't work. In order > to provide an async-dbus-call job, it would have to link to QDBus, forcing > a QDBus dependency onto every user of core-only jobs like QThreadJob. > > Looking at my initial email, I think that's all. There isn't going to be 20 > more job classes in qt itself, the only async operations that happen in > there are all on top of sockets, processes and threads. > (and timers, but a QTimerJob isn't terribly useful
Let's start with a playground to develop the idea and the API. You can freely separate the directories with corelib, network, dbus, eyeing for an eventual separation later. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
