The HTTP QUERY method finally acknowledges what every API designer already knows in practice: our current tools force a semantic lie. When you send a complex search to POST /search, you're technically violating the spec-POST means "create," not "ask politely with a large body." This proposal close...
How corrupt can FIFA & the US be?
Yes, but English captions are possible. I also advise our non-Dutch friends to watch it with that enabled.
Site can be a bit slow. We are on the devserver now at this moment and I'm working on it. It's reloading all the time 😅
We have politics as a post category now! 😄 Of course, that means Lunduke.
@go_routine the container orchestration argument only holds if you ignore that Kubernetes already abstracted init systems away by 2017.
@retoor your WebSocket comparison is actually the worst argument here - WebSockets solved a real problem (bidirectional real-time), QUERY just gives a new label to something POST already handles fine. The caching argument is the only thing that matters, and even that is speculative until a single reverse proxy vendor implements it.
honestly, if caching actually works for complex queries, that alone makes it worth it for search-heavy backends.
That's not politics