9

我有疑问我应该如何使用QEventLoop. 我有 2 段代码,它们都为我工作(下载网络资源)。

第一:

QNetworkAccessManager *manager = new QNetworkAccessManager( this );
QNetworkRequest request;
request.setUrl(QUrl(url));
request.setRawHeader("User-Agent", "Mozilla Firefox");
connect(manager, SIGNAL(finished(QNetworkReply*)),this,SLOT(replyFinished(QNetworkReply*)));
manager->get( request )  ;

QEventLoop loop;
connect(manager, SIGNAL(finished(QNetworkReply*)),&loop, SLOT(quit()));
loop.exec();

第二个:

QNetworkAccessManager *manager = new QNetworkAccessManager( this );
QNetworkRequest request;
request.setUrl(QUrl(url));
request.setRawHeader("User-Agent", "Mozilla Firefox");
manager->get( request )  ;

QEventLoop loop;
connect(manager, SIGNAL(finished(QNetworkReply*)),this, SLOT(replyFinished(QNetworkReply*)));
loop.exec();

我想知道我应该使用哪一个。我的意思是,在发出信号后,事件循环是否会在第二个中退出?还是我必须quit()像第一个一样打电话?我在某处找到了第二个解决方案,但对我来说似乎不合适,所以我将其修改为第一段代码。

4

2 回答 2

3

我同意@Mher-Didaryan 的观点——事件循环由loop.exec();第二个代码片段中的代码行开始——永远不会退出。这是因为 SIGNAL 和 SLOT 之间的connect()是针对与通过 指示的事件循环不同的事件循环完成的EventLoop loop;

在第一个代码片段的情况下,逻辑取决于finished(QNetworkReply*)与发送到两个不同事件循环的同一个 GET 请求相关联的信号。但很有可能

    connect(manager, SIGNAL(finished(QNetworkReply*)),&loop, SLOT(quit()));

可以在manager->get( request ) ;发出finished(QNetworkReply*)信号后执行。也许它可能发生在涉及非常小的文件或响应的 GET 类型的 HTTP 操作中。在这种情况下,loop.exec();第一个代码片段中的事件循环也不会退出。我想这也是@Mher-Didaryan 在他的回答中提出的问题。

也许您也可以使用下面的 QEventLoop 逻辑来处理以下负面执行场景

  1. GET 请求超时(比如由于网络连接问题)
  2. 来自网络服务器端的错误类型响应

    QNetworkAccessManager *manager = new QNetworkAccessManager(this);
    QNetworkRequest request;
    QEventLoop loop;
    QTimer getTimer; // let's use a 10 second period for timing out the GET opn
    request.setUrl(QUrl(url));
    request.setRawHeader("User-Agent", "Mozilla Firefox");
    // connect the timeout() signal of getTimer object to quit() slot of event loop
    QTimer::connect(&getTimer,SIGNAL(timeout()),&loop, SLOT(quit()));
    QObject::connect(manager, SIGNAL(finished(QNetworkReply*)),&loop, SLOT(quit()));
    QNetworkReply *resp = manager->get( request );        
    getTimer.start(10000); // 10000 milliSeconds wait period for get() method to work properly
    loop.exec();
    
    if(NULL == resp)
    {
        // Error. we probably timed out i.e SIGNAL(finished()) did not happen
        // this handles above indicated case (1)
        return -1; // or return some timeout related error value
    }
    else if( QNetworkReply::NoError != resp->error() )
    {
        // Error - SIGNAL(finished()) was raised but get() opn failed & returned with error
        // Refer http://doc.qt.io/qt-4.8/qnetworkreply.html#NetworkError-enum
        // This section of code handles above indicated case (2)
    }
    else
    {
        // get() operation was Successful !.
        // read the response available in the 'resp' variable as a QString & parse it. 
        // Obtain the necessary result and etc.
    }
    
    delete resp;
    delete manager;
    
于 2017-07-24T16:58:45.313 回答
1

在您的第二个示例中,事件循环将永远不会退出,而在您的第一个示例中,循环将在finished(QNetworkReply*)发出时退出。但是,如果在您将循环的退出连接到它之前manager->get( request );导致发出信号怎么办?finished(QNetworkReply*)

QNetworkAccessManager *manager = new QNetworkAccessManager( this );
QNetworkRequest request;
QEventLoop loop;
request.setUrl(QUrl(url));
request.setRawHeader("User-Agent", "Mozilla Firefox");
connect(manager, SIGNAL(finished(QNetworkReply*)),this,SLOT(replyFinished(QNetworkReply*)));
connect(manager, SIGNAL(finished(QNetworkReply*)),&loop, SLOT(quit()));
manager->get( request )  ;

loop.exec();

而且您还需要以某种方式处理经理根本不发出SIGNAL(finished(QNetworkReply*))的情况。

于 2017-01-01T17:50:14.510 回答