> On Jan 18, 2019, at 3:58 PM, Josh Graessley <jgraess...@apple.com> wrote: > > There is an implication here that a WebSocket API would support both a client > and a server.
Yes, server-side support would be very valuable for P2P use cases. > Does your radar explicitly ask for client and server? Do you happen to have > the radar number handy? Drat, it appears I didn’t actually get around to filing this, since I can’t find it in the BugReporter website. :( I’ve just filed a request as rdar://47430997 <rdar://47430997>. > WebSockets will provide framing, which can make some things easier but it > won’t help with TLS, especially when it comes to each side validating the > identity of the peer. If it’s layered on NSURLSession, then TLS is mostly taken care of on the client side. The server implementation would hopefully implement its side of the TLS handshake too. For P2P use there are of course difficulties in establishing trust, but having the protocol layer taken care of would still be a big step up for developers. —Jens (who has had to implement WebSocket on iOS/Mac 3 times now and doesn’t want to do it again)
_______________________________________________ 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/archive%40mail-archive.com This email sent to arch...@mail-archive.com
