thread with socket?

[triperzonak]

You would only need to call it if you wanted to use sockets in a non-blocking way on a separate thread.

yeah thats what i need.. so i will add exec() then?

i will just call it pass some parameter and execute, I dont need the return data i dont even need to test if the socket connects or not I want to let the thread do that and the application do what it should do.. Calling the socket blocks the GUI so i put it in a thread but if i need to put thread->wait() it will block GUI too..

im just avoiding to call it as binary but if it will block the GUI then i will reconsider it..

[caduel]

Use QSocketNotifier.
No need to create a separate thread. (You still may to so, if you want, though.)

HTH

[yuriry]

yeah thats what i need.. so i will add exec() then?

exec() is only required if you want to start an event loop on a thread. If you used QTcpSocket in conjunction with readyRead signal then you would need an event loop. But if you use Linux sockets, and I assume you do NOT use select/poll, just read/write, then you use them in a blocking fashion and your code should be similar to this example http://doc.trolltech.com/4.4/network...uneclient.html Even if sockets are used there in a blocking way, GUI thread does not block because blocking read/write calls occur on a separate thread.

And as caduel pointed out, there is a way to achieve non-blocking behavior without creating extra threads, but it seems that it is not an option for you because you are just integrating existing code and do not want to do many changes to it.