Paulo Lopes

We need to regenerate the manuals. This time just store them as asciidoc instead of attempting to convert to markdown and let github render them.

@vietj this is a thread related failure. I think you're the most skilled person to review it at the moment. The failure happens on: ``` Starting test: SockJSSessionTest#testNoDeadlockWhenWritingFromAnotherThreadWithWebsocketTransport 2018384 38975...

I was just thinking, at a high level, lets consider that we introduce a factory in the router itself like: ```java // Router.java coFactory(Function factory); ``` As the router creates...

In this example, the co routine handle is dependent on the router instance, you could mix by having several routers and use `subRouter()` to merge them. Alternatively... a more verbose...

Or split into a chain: ```java router .route("/xyz") .withCoroutineFactory(Kotlin) .handler({ ctx -> ctx.next() }) ``` In this case we can have again the `handler` like in the general API.

Yes, that's just me writting down in english what I expect the code will be doing :) `handlerFactory` is good and closer to our APIs. This method would then wrap...

@vincentfree that was more or less the original concept I wrote, that the coroutine factory would be fixed per router. The different here is that you're saying that this factory...

I'm looking at the `Router` and `Route` interfaces in order to have this at described using the `Router.create(vertx, factory)` it means that we will need to introduce generics on pretty...

@vietj the idea I was describing was to attempt to have a common way we could use not only with kotlin but also blocking, loom, executors, etc... Yet I was...

@hantsy that is totally possible, but it requires a bit more maintenance. Such router would need to be created on this project https://github.com/vert-x3/vertx-lang-kotlin but it isn't generated like the rest...