3 ms·
Writing a custom http router is kinda contra to the point of using a library, no? I don't want to bother with writing my own router and this was one of the few
by zaarn 9y ago
Writing a custom http router is kinda contra to the point of using a library, no?
I don't want to bother with writing my own router and this was one of the few times I had problems.
I think even if I wrote my own framework, I would eventually end up having to hack around it anyway when I inevitably need to do something the framework I wrote just fundamentally can't and I suggest this will be the case for your custom implementation too.
- heavenlyblue 9y agoSo don't evolve your project based on HTTP stack more than an HTTP stack may allow you to. Suddenly, you'd like to have real-time comm? Don't add WebSockets, simply because they fit right above the whole of your stack based on HTTP. Use TCP. There's a very gentle balance between using what you've already got and introducing a set of newer entities into the system; and sadly this is not always that clear, which one you should use.
- zaarn 9y agoYes and that's quite obvious. However, frameworks are stil a limiting fact in code. If I use a framework it won't let me do certain things. Which means I have to hack around or introduce newer entities/dependencies. A balance must be found, in one of the earlier examples, a quick hack was easier.