Back to product page
- Introduction
- License agreement
- Classes
- Enumerations
- Exceptions
- WeOnlyDo.Server.WebServer
- WeOnlyDo.Server.WebHeader
- WeOnlyDo.Server.WebHeaders
- WeOnlyDo.Server.WebRequest
- WeOnlyDo.Server.WebResponse
- WeOnlyDo.Server.WebSessions
- WeOnlyDo.Server.WebSessionVar
- WeOnlyDo.Server.WebSessionVars
- WeOnlyDo.Server.WebUpload
- WeOnlyDo.Server.WebUploads
- WeOnlyDo.Server.WebUser
- WeOnlyDo.Server.WebUsers
- How to get support?
WeOnlyDo.Server.WebServer
Main wodWebServer.NET object.
Remarks
wodWebServer.NET implements server side of HTTP and HTTPS protocols (HTTPServer). It's main purpose is to serve HTML pages, GIF/JPG/PNG images, documents, and other resources that are accessible through Browser clients (such as Internet Explorer, Mozilla Firefox, Netscape etc..). It is robust, easy to use, fast, and can be used in all environments that support .NET technology. It serves both static pages, as well as dynamically created ones.wodWebServer.NET runs using Request/Response objects model - whatever client sends is parsed and stored to Request object. When you're ready to deliver response, you just need to populate Response object - such as Body property, StatusCode, and that it. If you're fast and can do it from within RequestDone event, then you don't even have to call any Send methods - it's delivered automaticaly.
- support for HTTP and HTTPS protocols (SSL2/SSL3/TLS)
- ASP.NET support - you can serve ASPx pages from within your application
- complete information on connected users - get their originating IP address, originating port, total connected time...
- choose either Automatic content delivery (sit back and enjoy) or manual - in which case you define virtually everything that is sent
- parsing of query variables, posted data for easy access
- can be used as standalone, or together with other WEB server (such as Apache, IIS...) by running on another port
- ........ and much more