site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=MwDPfBWPZ4D+IavX/+ JM6KgxRS6usYIYi908+umrW98=; b=XtyIiQGA02dxk+uPomgHszWFJOKOEgw09j DjvcR5qyZFfmEszFG8rshlvR2wOfrIjfCscy8Av8y4wOBIG/qnj+OWrfxH1GHW7z B763P+Iv3AY3PF36Slk514yTtrj1VwUVAFzP/sRsplPwOEmBaAnkHE3B5T53ukHa 2vDpXXsSPBFaLS02TpVUJ8pC0T5R0/2Kqt1ADRNCn/NMPLGZ3nR0axFlyowwW6aZ HLR/l+rWGaAmW8sZZIYrk/FqvewxlrKa+PgOSqxRnL7wFGiSsRcoMuhdwDw/q+Ia R3i2ZjYCPSoi3SJBNFudkcPW3CxupaCJ3rhdv0szfM6WiRd+pSdw==

On Jul 11, 2017, at 12:45 PM, Tom Pusateri <pusateri@bangj.com> 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 (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com