Qt QNetworkAccessManager and multiple QNetworkReply

I have two get QNetworkRequest.

I want to handle finished signals from different methods.

For example this is code in

  MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent), ui(new Ui::MainWindow)

    connect(nam, SIGNAL(finished(QNetworkReply*)), this, SLOT(GetUserDataCompleted(QNetworkReply*)));

    connect(nam, SIGNAL(finished(QNetworkReply*)), this, SLOT(GetMessagesCompleted(QNetworkReply*)));

This my one method

I have tried replay->deleteLater(); but same result

Please advice me something useful

void MainWindow::GetUserDataCompleted(QNetworkReply *replay)
    if(replay->error() == QNetworkReply::NoError)
        QString getData = replay->readAll();
        QMessageBox msg;

        if(getData == "1")
            msg.setText("User Is not Exits");
            QDomDocument doc;

                QDomElement domElem = doc.documentElement();

                QDomNode n = domElem.firstChild();
                while(!n.isNull()) {
                    QDomElement e = n.toElement(); // try to convert the node to an element.
                    if(!e.isNull()) {
                    n = n.nextSibling();



You can create a RequestSender class whose role is looking after requests.

Each RequestSender object will handle one unique request. While creating the QNetworkRequest that will be sent, the RequestSender will "tag" its own request with the originatingObject attribute. This attribute indicates which object sent the request. When a RequestSender object receives a reply, it will look if it is the sender of the request via the originatingObject attribute. For further informations about originatingObject, you can refer to the documentation here : http://qt-project.org/doc/qt-4.8/qnetworkrequest.html#originatingObject

Below is an example of what you can do.

requestsender.hpp :

class RequestSender {
        void createRequest(/* Request parameters */);

    public slots:
        void endRequest(QNetworkReply* replay);

requestsender.cpp :

RequestSender::RequestSender() {
    connect(nam, SIGNAL(finished(QNetworkReply*)), this, SLOT(endRequest(QNetworkReply*)));

RequestSender::~RequestSender() {
    disconnect(nam, SIGNAL(finished(QNetworkReply*)), this, SLOT(endRequest(QNetworkReply*)));

void RequestSender::createRequest(/* Request parameters */) {
    QNetworkRequest * myRequest = 0;

    // Build myRequest with the request parameters



void RequestSender::endRequest(QNetworkReply* replay) {
    if (replay->request().originatingObject() != this) {
        // That's not the request sent by the object -> stop the method here !

    // Treatments on replay

Every operation you do with your QNetworkAccessManager will return a QNetworkReply. This has also has an signal finished(). Maybe you can connect this signal to your different slots.

Need Your Help

Setting Transaction Isolation Level in Berkeley DB Java Edition for Distributed Transactions (XA)

jta isolation-level distributed-transactions berkeley-db-je xa

I am using distributed transactions in a BDB JE application to coordinate transactions across multiple BDB JE environments. I want to set the transaction isolation level to serializable. To begin