|
|
1 day ago | |
|---|---|---|
| .. | ||
| src | 1 day ago | |
| .gitignore | 8 months ago | |
| Benchmarks.sln | 1 month ago | |
| README.md | 1 month ago | |
| benchmark_config.json | 1 week ago | |
| config.toml | 1 month ago | |
| touchsocket-http.dockerfile | 2 weeks ago | |
| touchsocket-http31.dockerfile | 2 weeks ago | |
| touchsocket-httpplatform.dockerfile | 2 weeks ago | |
| touchsocket-webapi31.dockerfile | 2 weeks ago | |
| touchsocket.dockerfile | 2 weeks ago | |
See touchsocket for more information.
touchsocket.webapi (TouchSocketWebApi) – WebApi style.touchsocket.webapi31 (TouchSocketWebApi31) – WebApi targeting .NET 8.touchsocket.http (TouchSocketHttp) – Minimal HTTP implementation.touchsocket.http31 (TouchSocketHttp31) – Minimal HTTP targeting .NET 8.touchsocket.httpplatform (TouchSocketHttpPlatform) – High-performance custom pipeline-based HTTP server focusing on low-level parsing and zero-allocation response writing.Language / Runtime
All variants implement:
/plaintext – Returns a plain text "Hello, World!" response./json – Returns a JSON object {"message": "Hello, World!"}.The httpplatform variant manually parses request lines and headers via System.IO.Pipelines for maximum throughput.
Each variant has a dedicated Dockerfile named:
touchsocket.dockerfile (webapi)touchsocket-webapi31.dockerfiletouchsocket-http.dockerfiletouchsocket-http31.dockerfiletouchsocket-httpplatform.dockerfileThe httpplatform variant is intended for benchmarking raw server performance. It omits higher-level abstractions to reduce overhead.