Edgar Espina
Edgar Espina
I want to revisit and see if we can improve it. Ideally, would like do the same for completable future
> Huge thumbs up for the API refactoring for Contect -> Request + Response! Going to keep Context in 3.x, because feel it is better the single argument handler: get("/",...
> Would removing ASM slow performance down? A bit on some specific use cases, but not for usage on real application. > Would be good to add a jackson alternative...
> dsljson has a reflection option, which is still quite a bit faster. cool, I didn't know it. > If it's just basic auth or jwt (via e.g. jjwt) then...
I'm not going to say anything about Quarkus... 😄 > Is it a documentation issue? The session store doesn't feel like authentication so maybe I'm misunderstanding it... Integrates the HTTP...
The API is: io.jooby.Context, a server implementation must provide a context. It is impossible to require more than io.jooby.Context there are all type of oddities between servers.
@jonnii master branch is running on Kotlin 1.4, so next release (2.9.0) comes with it and yea, no work has been done yet on 3.x 👍
@ravihara Log4j2 is supported in Jooby 2.x today https://jooby.io/#configuration-logging-log4j2 and you can use `log4j.json` to configure it.
Oh got it. will check what vertx does and yes! would like to remove logging from core
will definitely look at minlog, but yea that is the issue with logging and config: we need to add a new contract/abstraction for each of them... which I don't like...