> On Jul 11, 2017, at 12:45 PM, Tom Pusateri <[email protected]> wrote: > > Since you did say iOS (and therefore wifi), I would suggest a unicast > approach for the data, especially given the push to encrypt everything these > days. Using IP Multicast with encryption is a bigger challenge with key > distribution. Using TLS over TCP unicast is pretty simple with Apple’s > NSURLSession.
I agree. Also, handling packet retransmission in multicast seems like it would be tricky — if a recipient can tell that it’s lost a packet then it can sent a (unicast) retransmit request back to the sender, who can (unicast) send it again … but there are cases where the recipient doesn’t know it was supposed to get a packet that it didn’t get. I’ve built a small P2P system where peers open TCP sockets on demand when they have something to send. It worked pretty well for very small numbers of peers, but I never got around to any scalability testing. This is likely the same approach MPC uses. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
