Thanks for the fast reply.
Yes, the server requires to receive the heartbeats in every 10 seconds.
Let me write an example. It's based on a wireshark capture.
- The server listens on 4 ports 8020, 8019, 8008, 8003. These ports are reserved (this is a switch online all the time, it doesn't really matter I think).
- The client sends the first heartbeat from ports: 53036, 53037, 53038, 53039 to ports 8020, 8019, 8008, 8003. This repeats in every 10 seconds.
- When server receives them replies from ports 8020, 8019, 8008, 8003 to ports 53036, 53037, 53038, 53039.
- If there are test results ready on the server it sends them to ports 53036, 53037, 53038, 53039.
If possible I would like / have to write a single client. /li
| [reply] |
Hm. It is still not clear from your description that the heartbeats and data transfers take place concurrently.
- Does a test result data transfer take longer than 10 seconds?
- Do you actually see a heartbeat get sent from client to server, whilst the a data transfer is in progress from server to client?
(I'm not sure that this is even possible!)
- If so, what happens about the servers reply to the heartbeat?
Does it suspend the data transfer in order to send the reply?
Or does the reply get delayed until after the transfer completes?
Or does the server ignore heartbeats sent whilst a data transfer is in progress?
I suspect that the logic is more likely, the client sends a heartbeat every 10 seconds unless a data transfer is currently in progress.
If that is the case, the requirements are actually quite simple. But as you've described so far, I don't think they are possible, using threads processes or a select loop.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
| [reply] |
