The second part of the C# Ping Tutorial is up. At the moment it doesn't have much in the way of solid implementation, but this is a series of posts so expect more. It is quite a good post because he talks about what Ping packets look like and where they are on the communications stack.

Anyway to quote the post.

Let us start out by looking at requirements of the Ping client. Basically, the task of the tool is to find out if a specified server is alive, and on the network. The way it achieves this is by sending an echo packet to the server. The server responds with an echo response. If the server responds within a certain time interval, then we can assume that there is network connectivity from the client to the server. If it doesnt respond, then it could indicate a variety of things that could be wrong

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)

Enter your email

Mastodon Book a consultation