I have spent the last couple of evenings learning about Rust and trying it out. Wrote a simple cli calculator as a first thing and thought I would improve it by making it available over http.

I was actually a bit surprised to find that there was no http tooling in the standard library, and searching online gave me an overload of information on different libraries and frameworks.

I ended up implementing my own simple HTTP server, might as well as this is a learning project.

Now I have it working, and while it isn't perfect or done, I thought that this would be a good time to check what things I am doing wrong/badly.

Which is why I am here, would love to get some pointers on it all to make sure I am going in the right direction in the future.

The project is hosted here: https://github.com/Tebro/rsimple_http

you are viewing a single comment's thread
view the rest of the comments

[–] stifle867@programming.dev 7 points 11 months ago (1 children)

You're not crazy. HTTP is commonly part of standard libraries nowadays.

[–] taladar@sh.itjust.works 5 points 11 months ago (1 children)

Only in languages that do not consider long term support before adding stuff to the standard library.

There really isn't a good reason to add things like protocols that change significantly over time in a standard library.

[–] Jummit@lemmy.one 2 points 11 months ago* (last edited 11 months ago) (1 children)

I doubt TCP/UDP or basic HTTP requests will change much, but I guess it depends on how high-level the API is.

[–] sugar_in_your_tea@sh.itjust.works 2 points 11 months ago

HTTP has changed quite a bit from HTTP/1.0 -> 2.0.