QProcess+TcpSocket

[Fastman]

So what's the point of monitoring the socket? You don't even need the socket at all... you can use stdin/stdout to transfer all the data you need.

Each connection of the client and performance of process is processed in a separate stream:

Server::Server(QObject *parent):QTcpServer(parent)
{
 
	if (!listen(QHostAddress::Any,1715)) {
		return;
	}
 
}
 
Server::~Server()
{
 
}
 
void Server::incomingConnection(int socketDescriptor)
{
	FortuneThread *thread = new FortuneThread(socketDescriptor,this);
	thread->start();	
}

Server::Server(QObject *parent):QTcpServer(parent)
{

	if (!listen(QHostAddress::Any,1715)) {
		return;
	}

}

Server::~Server()
{

}

void Server::incomingConnection(int socketDescriptor)
{
	FortuneThread *thread = new FortuneThread(socketDescriptor,this);
	thread->start();	
}

To copy to clipboard, switch view to plain text mode 

void FortuneThread::run()
{
	Connection connection;
	if(!connection.setSocketDescriptor(socketDescriptor))
	{
		emit error(connection.error());
		return;
	}
	connect(&connection, SIGNAL(disconnected()), this, SLOT(deleteConnection()));
	exec();
}

void FortuneThread::run()
{
	Connection connection;
	if(!connection.setSocketDescriptor(socketDescriptor))
	{
		emit error(connection.error());
		return;
	}
	connect(&connection, SIGNAL(disconnected()), this, SLOT(deleteConnection()));
	exec();
}

To copy to clipboard, switch view to plain text mode 

[wysota]

I don't see a relation to what the busy loop here... If a connection drops, you'll get an error trying to write to the socket, I don't see what waitForDisconnected() is needed for... And processing application events from within a worker thread (because I assume it is the thread that calls processEvents()) seems suspicious.

[Fastman]

I don't see a relation to what the busy loop here... If a connection drops, you'll get an error trying to write to the socket, I don't see what waitForDisconnected() is needed for... And processing application events from within a worker thread (because I assume it is the thread that calls processEvents()) seems suspicious.

if i'am comment QCoreApplication:rocessEvents();
this->state() on that does not change

[wysota]

I shall explain. The client has an adjustment - how many simultaneously streams to start. The client considers quantity simultaneously started streams and holds connection until then while process of coding of a file will be completed or there will be a mistake. The server is located on unix, and the client on Windows. Earlier this system on C has been written. But I have decided to try with studying QT to copy this part on QT/C ++

But what does waitForDisconnected() do for you? I don't see any point in using it... You have a slot connected to the disconnected() signal, so why wait for the signal in a busy loop?

if i'am comment QCoreApplication:rocessEvents();
this->state() on that does not change

This is obvious, because timers won't fire and the state won't be able to change.

Maybe processEvents() is wise enough to call the appropriate event queue based on the current thread id and thanks to that your application doesn't crash...

[Fastman]

I shall explain. The client has an adjustment - how many simultaneously streams to start. The client considers quantity simultaneously started streams and holds connection until then while process of coding of a file will be completed or there will be a mistake. The server is located on unix, and the client on Windows. Earlier this system on C has been written. But I have decided to try with studying QT to copy this part on QT/C ++