Wiseguy
Re: Thread, Timer and Socket. Comuication problem
Very hard to tell with out seeing the code.
Specially, since you might THINK you are doing something, but really doing something else, mostly due to problems with thread affinity, which sounds to me to be the problem her as well.
It will be good if you could post relevant code.
Specially where you create the objects you are talking about.
==========================signature=============== ==================
S.O.L.I.D principles (use them!):
https://en.wikipedia.org/wiki/SOLID_...iented_design)
Do you write clean code? - if you are TDD'ing then maybe, if not, your not writing clean code.
Advanced user
Re: Thread, Timer and Socket. Comuication problem
Hi,
Sorry, but I have 24 files only to manage the communication and 4 more files to manage the application and the thread. So, I can't attach the files here.
I'm developing the Modbus protocol.
The timer is in the main thread
The class that has the socket is in the main thread
The other thread emits a signal that is catched in the main thread usign Queued connection.
Thanks,
Òscar Llarch i Galán
Wiseguy
Re: Thread, Timer and Socket. Comuication problem
That is why I said relevant code - which means showing in code snippets the same you were explaining in words.So, I can't attach the files here.
So lets try to make things clear:
You have a socket and a polling timer in the main thread.
You have a worker thread, that emits a signal, which fires a slot in the main thread that sends something through a socket is that correct?
And then, again, what is the problem you are having?
==========================signature=============== ==================
S.O.L.I.D principles (use them!):
https://en.wikipedia.org/wiki/SOLID_...iented_design)
Do you write clean code? - if you are TDD'ing then maybe, if not, your not writing clean code.
Advanced user
Re: Thread, Timer and Socket. Comuication problem
Hi,
Yes, this is correct.You have a socket and a polling timer in the main thread.
You have a worker thread, that emits a signal, which fires a slot in the main thread that sends something through a socket is that correct?
The class that contain the socket has a QQueue that enqueue the message sended, so the messages enqueued by the timer and the thread(that will be different) stay in a FIFO.And then, again, what is the problem you are having?
Then, when the socket recives a response from the client, I have to verify that the message sended corresponds to the response got. So dequeue the sended message and compare to the recived.
May this work? I think yes, but I'm having troubles:
Imagin that the response of the client tells me to stop the worker thread, so I sotp it, but the timer is still sending messages. Then, one of the responses can tell me to start the thread anagin.
Stops ok but it don't start again.
Thanks,
Òscar Llarch i Galán
Wiseguy
Re: Thread, Timer and Socket. Comuication problem
Well, why can't you stop the time when you stop the worker thread?Imagin that the response of the client tells me to stop the worker thread, so I sotp it, but the timer is still sending messages. Then, one of the responses can tell me to start the thread anagin.
But where is the problem?Stops ok but it don't start again.
If you receive a message from the socket to start the thread again, what stops you from restarting your thread again?
==========================signature=============== ==================
S.O.L.I.D principles (use them!):
https://en.wikipedia.org/wiki/SOLID_...iented_design)
Do you write clean code? - if you are TDD'ing then maybe, if not, your not writing clean code.
Posting Permissions
Reply With Quote
Bookmarks