Implementing an asynchronous TCP client
As it has already been mentioned in the introduction section of this chapter, the simplest asynchronous client is structurally more complex than equivalent synchronous one. When we add a feature such as request canceling to the asynchronous client, it becomes even more complex.
In this recipe, we'll consider an asynchronous TCP client application supporting the asynchronous execution of the requests and request canceling functionality. Here is the list of requirements the application will fulfill:
- Input from the user should be processed in a separate thread—the user interface thread. This thread should never be blocked for a noticeable amount of time.
- The user should be able to issue multiple requests to different servers.
- The user should be able to issue a new request before the previously issued requests complete.
- The user should be able to cancel the previously issued requests before they complete.
How to do it…
As our application needs...
