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
-
@Lor-inc what about instead of routing, you can pass the arguments as is to another function to handle it seperately?
Also idk wss://localhost/websocket is better than just wss://localhost -
@melezorus34 At this point I want to do it this way less because I need to and more because it has no technical limitations or disadvantages and it pisses me off to no end how it hasn't been solved yet.
HTTP response code cheat sheet
(From /r/Programmer humor)
You see a web, I see:
CLIENT: TCP SYN
SERVER: TCP SYN ACK
CLIENT: HTTP Get
SERVER: HTTP Response
...
CLIENT...
CGI is fun, websockets are fun, why on earth is it so fucking hard to have both of them with proper switching using at most one extra program apart from my handlers?
By proper switching I mean that you actually track connections and upgrade headers to decide what to do, rather than forcing websocket connections onto a separate HTTP resource just to tell the difference.
rant
websocket
cgi
http