Welcome to part three! As promised heres a description of the inner workings.  I’m sick to death of typing SocketAsyncEventArgs so from now on I will refer to it as SAEA. BocketPool The BocketPool has an interesting name and with it an interesting constructor! It takes the following parameters: number: The number of items to create in the BocketPool. size: The size of each buffer in bytes. callback: A callback function which is invoked whenever the SAEA object completes its operation. 1 2 3 4 5 6 type[...]

Welcome to part three!As promised heres a description of the inner workings. I’m sick to death of typing SocketAsyncEventArgs so from now on I will refer to it as SAEA.

Welcome to part two Lets jump in at the deep end and take a look at some code… When you look at the method syntax for the xxxAsync methods you will notice they return a boolean value that indicates if the method completed synchronously, this means that you have to check the return value every time you use one of the methods and invoke the callback yourself if it completes synchronously.  In practice this hardly ever happens, and normally only on a send operation.  But as it is a possibility we will add m[...]

Welcome to part two Part 1 Part 2 Part 3 Part 4 Lets jump in at the deep end and take a look at some code… When you look at the method syntax for the xxxAsync methods you will notice they return a boolean value that indicates if the method completed synchronously, this means that [...]

Welcome to part twoLets jump in at the deep end and take a look at some code… When you look at the method syntax for the xxxAsync methods you will notice they return a boolean value that indicates if the method completed synchronously, this means that you have to check the return value every time you use one of the methods and invoke the callback yourself if it completes synchronously. In practice this hardly ever happens, and normally only on a send operation. But as it is a possibility we will add[...]