Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Oh dear, here we go again.
Three ideas, that it takes just a few seconds to dismiss as unworkable. Whether or not that's possible is irrelevant ... that is not what the OP seems to be doing. To quote him: ... You quote only section 2 of the OPs response to my questions. Selective amnesia; or did ADHD kick in before you got to section 3? Let's quote him a little more: 2) The client sends the first heartbeat from ports: 53036, 53037, 53038, 53039 to ports 8020, 8019, 8008, 8003. This repeats in every 10 seconds. See it? The source/destination pairs are the same in both directions (Ie. for the client to server heartbeats and the server to client transfers) which makes the question of whether two local processes can use the same local port concurrently very relevant! Oh, and do note that in my sketch, there's just one program anyway. You made two suggestions in that post, the second of which used multiple processes, with separate processes for the heartbeats and data transfers. And both of which cannot possibly work for the OPs requirements as described. 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".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^4: UDP connection
by BrowserUk
|
|