Asynchronous TCP/IP, Part 2 скачать в хорошем качестве

Asynchronous TCP/IP, Part 2

This series: Live coding to https://github.com/StephenClearyExamp... Developing an asynchronous TCP/IP server and client. Discussing TCP/IP protocol design. Discussing some harder concepts in async/await. Part 2: Sending and receiving data over a connected socket. Using System.IO.Pipelines to send data over a connected socket and handle partial sends. Code changes: https://github.com/StephenClearyExamp... Resources mentioned in this video: Project Bedrock: https://github.com/davidfowl/BedrockF... Socket class documentation: https://docs.microsoft.com/en-us/dotn... WSA-style Berkeley API: https://docs.microsoft.com/en-us/wind... TCP/IP Socket FAQ: https://blog.stephencleary.com/2009/0... TcpView: https://docs.microsoft.com/en-us/sysi... WinSock error codes: https://docs.microsoft.com/en-us/wind... System.IO.Pipelines: https://docs.microsoft.com/en-us/dotn... 0:00 Awkwardly waiting 0:11 Intro 1:05 Shoutout to Project Bedrock 2:16 How the Socket class relates to the Berkeley Sockets API 6:23 Running our client and server and observing ports 9:44 Sending data from the client to the server 12:34 Reading data from a connected socket on the server 14:33 Don't use Socket.Connected! 17:19 Reading data from a connected socket 25:07 Incorrect reading and writing can work on localhost 26:42 The code is wrongly assuming message boundaries are preserved 27:39 Demonstrating one problem with the code 29:00 TCP/IP provides a stream of bytes, not a stream of messages 32:05 Preserving message boundaries using message framing 37:19 Partial sends are also possible 40:02 Deciding to use System.IO.Pipelines 41:30 Messy code necessary for reading and writing without Pipelines 43:10 Using System.IO.Pipelines to write to the socket, handling partial sends 46:49 (Do not use Socket example code in production) 48:16 Using System.IO.Pipelines to write to the socket, handling partial sends 1:03:02 Outtro