Edgar Espina

Eureka documentation is not good. I tried the eureka client... but don't think it works. More comments: - There isn't a clean example of how to do it without Spring...

Like it. I want to remove those loadClass checks from core and make this more modular (like it was in 1.x). The reason why I added like this was to...

Just realize that there is an API for custom types: https://www.javadoc.io/doc/io.jooby/jooby/latest/io/jooby/ResponseHandler.html ```java MyExtension { install(Jooby app) { app.responseHandler(...); } } ``` Rocker template engine uses a custom response handler: https://github.com/jooby-project/jooby/blob/2.x/modules/jooby-rocker/src/main/java/io/jooby/rocker/RockerModule.java#L45...

Yea, I can't pay two domains. Old doc is over `v1` path: https://jooby.io/v1/doc/#https

I don't own the domain anymore... didn't know it was still active and showing some v1 content :(

Tried everything... nothing works. They (go daddy) just don't care: >Hello there! > I just wanted to reach out because the seller has viewed the offer and has not responded...

Hi, I'm not sure we can ensure such behavior across web servers (netty, jetty, undertow). Also, client disconnect occurs all the time and mostly they are error we want to...

are you happy on how it works? Honestly, thought no one used it. Also, we had been discussing to move reactive to his own module (like we did in 1.x)....

Yea, we should support 3.x. What I'm not sure is to drop 2.x while we do it

Yea, non-blocking types don't work well with filters. It is documented here: https://jooby.io/#responses-nonblocking-limitations