Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Bubbles
I plan on publishing the git repo I'm working in. But not yet as I'm still applying wild refactors every week and the project is not stable enough to call it... a consistent thing.
I followed the RFC spec for HTTP/1.1 and Websockets. -
@OneOfSimpleMind I’ll keep this in mind, thanks!
-
@SortOfTested Yeah that's basically what HTTP/3 is actually: QUIC.
when your code is a mess but everything work out in the end
HTTP response code cheat sheet
(From /r/Programmer humor)
So here I am reinventing the wheel making an HTTP server in C.
Finished implementing HTTP/1.1 and WebSockets support and now I find out the current thingy is HTTP/2.
Well that's fine, I'll add support for that later. In fact I kinda dig it since it uses binary conventions instead of plain text ones.
I dig a little bit and find out there already is an HTTP/3 going around which uses UDP.
Why me.
rant
udp
http
tcp
c