Problem encountered in http server implementation

[tbscope]

What is the appropriate should the server wait for the request to arrive ?

That's the wrong question to ask, and here's why:
You can never know.

You can set a time out though to, for example, 10 seconds.

Here are the two techniques to deal with the data:
1. Asynchronous, or non-blocking. This is event driven. Every time data becomes available, the socket will post an event resulting in a signal (the readyRead signal)
If you connect a slot to this signal, you can use readLine, or any of the other read functions. In the mean time, the socket will do nothing except checking the buffers and it will not block the event queue.

2. Synchronous, or blocking. This is not event driven. The socket just waits for data te become available. It blocks the event queue and can almost only be used in threads.
Use the waitFor...() functions.

Suggestion: Do not use threads and certainly not the blocking functions unless you absolutely need to.

[ada10]

I used both the methods as you mentioned. In the asynchronous method I tried, the code looked like this -

clientConnection = tcpServer->nextPendingConnection();
 
    connect(clientConnection, SIGNAL(disconnected()),
                clientConnection, SLOT(deleteLater()));
 
    connect( clientConnection, SIGNAL(readyRead()),
             this, SLOT(readClient()) );

clientConnection = tcpServer->nextPendingConnection();

    connect(clientConnection, SIGNAL(disconnected()),
                clientConnection, SLOT(deleteLater()));

    connect( clientConnection, SIGNAL(readyRead()),
             this, SLOT(readClient()) );

To copy to clipboard, switch view to plain text mode 

where the readClient() slot implementation is as shown -

void serverwindow::readClient()
{
    QTcpSocket* clientSocket = (QTcpSocket*)sender();
 
   //pass this socket to a new thread which send some data to client
}

void serverwindow::readClient()
{
    QTcpSocket* clientSocket = (QTcpSocket*)sender();

   //pass this socket to a new thread which send some data to client
}

To copy to clipboard, switch view to plain text mode 

Here as I obtain some data on socket, I used to spawn a new thread with the socket reference as a parameter to the thread. This caused huge problems because that socket reference could not be "moved" to another thread. So this was the issue I faced with the asynchronous method.

So I used th synchronous method with waitForReadyRead() method with some parameter ( which is not the way code should be written; I understand ).
Certainly I know, the asynch method is better, but I could not find a solution to the above problem . If you could provide some solution to this, I would be happy to incorporate into my code.

[tbscope]

I'll try to write an example later today.