I did help, and a lot! While you didn’t explain why the newConnection() signal is emitted twice, you gave me a way to avoid counting the same request more than once, which is far better. I can now continue working on the tests.
I’ve posted the issue in the Qt Forums[1], to see if someone there has more input on why QTcpServer behaves the way it behaves. Again, many thanks. Adrian O Xoves, 7 de Marzo de 2013 15:31:31 Albert Astals Cid escribiu: > El Dimarts, 5 de març de 2013, a les 21:25:13, Adrián Chaves Fernández va > escriure: > There's no race condition at all between KJob and QNetworkAccessManager, i'd > say it's just that your code is assuming wrong stuff regarding how the > network > communication happens. > > Proof that there is no KJob/QNetworkAccessManager race condition is attached > in proof1.tar.bz2. As you can see in it, there is no KJob anywhere but you > still get "Already got this request!!!!!!!!!!!" debugs > > Proof that there is something wrong in your assumptions on how the network > communication happens is attached in proof2.tar.bz2. As you see there I'm not > sending any data in the post method and all is fine. (You can do the same in > your code by sending nothing in your post() method inside job.cpp) > > Hope this helps. > > Cheers, > Albert -------- [1] http://qt-project.org/forums/viewthread/25521/
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
