Is that a general rule, wysota? I was thinking if maybe a signal was emitted in the request method (not the complete, but maybe an error signal) that Qt wouldn't actually emit or queue the signal as there was no listeners at the time it was emitted.
Is that a general rule, wysota? I was thinking if maybe a signal was emitted in the request method (not the complete, but maybe an error signal) that Qt wouldn't actually emit or queue the signal as there was no listeners at the time it was emitted.
Trok (2nd January 2010)
I closed NOD32 and all the firewalls but I have still the same communique:
I suppose that the firewall don't block this operation, because I can send POST request by SOCKET correctly.Starting C:/Documents and Settings/Trok/Pulpit/Qt Progs/Test_gg/debug/Test_gg.exe...
NOD32 protected [MSAFD Tcpip [TCP/IP]]NOD32 protected [MSAFD Tcpip [UDP/IP]]NOD32 protected [MSAFD Tcpip [RAW/IP]]NOD32 protected [RSVP UDP Service Provider]NOD32 protected [RSVP TCP Service Provider]Test
""![]()
Last edited by wysota; 5th January 2010 at 15:08.
With networking classes - yes.
All "request" type of methods don't do anything. They just schedule execution.I was thinking if maybe a signal was emitted in the request method (not the complete, but maybe an error signal) that Qt wouldn't actually emit or queue the signal as there was no listeners at the time it was emitted.
Trok (2nd January 2010)
Small side note: Use QNetworkAccessManager. QHttp is deprecated.
Disclaimer: Although I work on Qt for Nokia, anything I post here is personal
waynew (21st March 2010)
Bookmarks