This project was started from ugly fun example. But this project is not a simple HTTP load balncer. We dont need it. We need to balance our application payload. So let we use somthing like a application bus to communicate with application logic.
Also there standard practice to use external crates(modules,libraries). But lot of them suffer from overprogramming, not clear implementation of specifications and unnecessary extra functionality. So i liked the starter point of project and i would like to use less external code in that project. Because "less code" is mean less errors and faster executon, which is main goal.
See the Borderland Project Wiki for full documentation, examples, and operational details.
You may be looking for:
Make sure you have cargo installed and run the command cargo run to boot up the server.
Visit locahost:8080 from your browser.
-
Say hello world - visit
localhost:8888/api/v1 -
Serve static files - visit
localhost:8888/files/index.html- this will serve theindex.htmlfile from thewwwfolder in the repo root. Place any other file insidewwwand they can be served similarly (using the/filesprefix - this will be configurable by the user in future, just like in Apache and Nginx).
- HTTP Scheme redirect to HTTPS by design
- Moved to MIO
- Routing
- Session handling
- Datastorage
- Application Bus
- Internal application logic
- Started profiling coz move to use MIO doesnt give good results
- HTTP to HTTPS redirect by design
- HTTPS part and threading
- Moved to MIO event based handling
- Detection plain HTTP by magic (similar as unix
filecommand) - Headers dump
- Small fixes to proper static content handling
$ab -n 5000 -kc 500 http://127.0.0.1:8000/
...
Requests per second: 14109.94 [#/sec] (mean)
Time per request: 35.436 [ms] (mean)
Time per request: 0.071 [ms] (mean, across all concurrent requests)It's sad (((
This work is licensed under the MIT license. See LICENSE for details.