4 ms·
I like. Simple, clean, the right idea. I don't see big advantages over one of the Jax-RS libraries, though. Those libraries pack in a lot, all of which you're
by ccleve 11y ago
I like. Simple, clean, the right idea.
I don't see big advantages over one of the Jax-RS libraries, though. Those libraries pack in a lot, all of which you're going to need if you build a serious app.
I think this library would be interesting if it could allow for easy swapping of a transport layer. If I could, for example, dump http for something faster with few code changes, that would be very cool.
- xaduha 11y ago> I don't see big advantages over one of the Jax-RS libraries, though. I do, at least potentially. JAX-RS frameworks that are currently on the market add too much overhead. https://www.techempower.com/benchmarks/#section=data-r11&hw=peak&test=json&f=jz6rk-1ekg-pag-jz6ro-0 https://www.techempower.com/benchmarks/#section=data-r11&hw=... https://github.com/TechEmpower/FrameworkBenchmarks/search?utf8=&q=javax.ws.rs&type=Code https://github.com/TechEmpower/FrameworkBenchmarks/search?ut...
- Roboprog 11y agoBingo. Yuck. I don't want to read the code for (let alone write) a bunch of do-nothing model objects. I want something that turns my result set into JSON ("there is no step 2"), assuming I am running an authenticated query. Of course, I also want something that runs my Javascript validation code server side, as well, but that's another story.