[Development] API review for a new QDnsResolver class

[morten.sorvig at nokia.com]

On Nov 4, 2011, at 9:37 PM, ext Thiago Macieira wrote:

> On Friday, 4 de November de 2011 21:01:30 Andre Somers wrote:
>> Me too. My point was, that we have slightly different patters for 
>> basically the same sort of thing in different places in Qt. QFuture is 
>> currently coupled with QtConcurrent, but is there a strong reason why 
>> is must be? I was not privy to that IRC chat, perhaps you could tell us 
>> the reasoning why it would not be possible?
> 
> There's no reason why it has to be coupled with Concurrent. Or, to put in 
> other words, it could be changed to work without Concurrent.
> 
> However, the problem is, it is currently too tightly coupled with 
> QtConcurrent. Unless someone is volunteering to do this work right now...


Actually, is it tightly coupled at all? qfutureinterface.h contains the (undocumented) backend class that run/map/filter uses to produce results for QFuture. That class could be polished up and documented if we want to use QFuture in other places.

Morten