[Qt-interest] QNetworkAccessManager in GUI thread

Thiago Macieira thiago at kde.org
Tue Feb 2 12:08:45 CET 2010


Em Terça-feira 2. Fevereiro 2010, às 00.04.40, Nitin Mahajan escreveu:
> The readAll() and the write() calls are the one which are spending
> significant amount of time, as reported by ltrace.
> 
> How to manage these operations, so that they do not freeze the UI?

There isn't a way.

The next step is to profile those functions and find out where they are spending 
so much time.

I guess the problem is the many levels of buffering that Qt has. Unfortunately, 
to solve that, we'll need to refactor much of the network code. I'd like to 
see that done, but it won't happen for Qt 4.7.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100202/af0d749b/attachment.bin 


More information about the Qt-interest-old mailing list