#Web client control how to#
#Web client control code#

BandWidthManager - Responsible for measuring time and computing transferred data to keep the desired speed.HttpAdvancedStream - Uses the events from base class to insert some wait time.WatchedStreamEventArgs - Event arguments for stream transfer events.WatchedStream - Serves as a proxy for given stream calling events before every read/write operation.This can be accomplished simply by slowing down read streams - first for the POST data and second for server response, so I created a stream proxy class slowing down read/write operations for a given stream held inside the proxy.

#Web client control code#

I also prepared some code which enables control bandwidth used by network communication. These classes are all you need to run simple HTTP requests with data uploading/downloading in both ways. HttpMessage - container for HTTP request or response including headers and data stream.HttpWebRequestConnection - implementation using standard WebRequest and WebResponse classes.HttpSocketConnection - new client implementation based on TCP sockets.HttpConnection - represents an abstract connection to the web server which can handle only one request at a time.I needed to create an abstract interface, which enables me to return to standard solution at any time. I didn't want to rewrite all my application but just to do some experiments first to ensure my idea is sustainable. HTTP protocol is not really complex, so why not just open a socket on port 80 and start communication? It didn't seem to be very difficult, but I found out standard classes load all output data into memory before send despite the face that the WebRequest class offers an output stream for POST data. My first reason for writing my own HTTP client library was the need to upload large files to the server and show the current upload speed. The reader should know the basics of HTTP protocol.

#Web client control how to#

This article is an example of how to do so. In these cases, we could not have another option but to write our own HTTP client implementation based on TCP sockets. NET programmers are familiar with classes like WebRequest, WebResponse or WebClient which are very useful, but sometimes one needs features they don't offer.

Download HttpLibrary with sample solution - 839.53 KBД¬ommunication over HTTP is a very common task.