Timeline for Best approach for near real time message passing from server to client across router?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 8, 2013 at 6:50 | answer | added | GrandmasterB | timeline score: 1 | |
Jul 8, 2013 at 3:28 | comment | added | user1724280 | @Guy -- UDP does seem like the right protocol. Especially given that my communication needs are extremely simple. Order is not important and the message only needs to be a few bits. However, if off the shelf communication libraries for TCP already exist to wrap a socket connection that can handle this, then that is the way to do it. A higher level library where the underlying mechanism handles all the difficulties is the cleanest. | |
Jul 8, 2013 at 3:18 | comment | added | Guy Sirton | Consider using UDP rather than TCP. You will still need to traverse the NAT so your clients will need to periodically ping the server and you will need some sort of acknowledgement mechanism but overall it should be simpler than TCP. | |
Jul 8, 2013 at 3:04 | comment | added | user1724280 | @LachlanB -- Yes I do understand that the network itself will be a limiting factor. However I just want to find the right software architecture to push through the message as fast as possible when possible. | |
Jul 8, 2013 at 2:41 | comment | added | Rocklan | As soon as you have the messages being passed over the internet you're at the mercy of it. It doesn't matter what language or clever code you've written, a congested network will cause you problems and it's completely out of your control. Your best bet is to have a very close look at the hardware side of things first. Check the link speed to and from servers and check what's in the contract in terms of guaranteed uptime and availability. Once you've got that sorted start looking at the code. | |
Jul 8, 2013 at 0:55 | comment | added | user1724280 | @ratchet freak No, the clients will not be able to communicate with each other. Sorry, to make it clearer they will all be on separate networks, but connected to the public Internet. | |
Jul 8, 2013 at 0:48 | review | First posts | |||
Jul 8, 2013 at 1:43 | |||||
Jul 8, 2013 at 0:31 | comment | added | ratchet freak | is it an option to have the clients communicate with each other? | |
Jul 8, 2013 at 0:29 | history | asked | user1724280 | CC BY-SA 3.0 |