This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[00:44:20] * ChanServ sets mode: +o temporalfox [00:53:12] <samsquanch> Hi Folks, can someone clarify something for me? I'm used to the way Akka does things when providing a Syncrhonous HTTP frontend and implementing it asynchonously [00:54:10] <samsquanch> In akka, when you get an HTTP request it is safely “blocked” for you by the underlying infrastructure, you get a “handle” to the client that you just pass around and the last guy closes it when he's donw [00:54:46] <samsquanch> With my vertx n00bness, the first thing I tried to do is send the HTTPServerRequest around on the eventBus, this is obviously not correct [00:55:36] <samsquanch> So say, my HTTP handler gets a request which can only be fulfilled by another service which lives asynchronously on the eventBus. Do I make a call to him and wrap it in a future? What is the proper way? [00:55:53] <samsquanch> The docs don't really explain this to me the way I understand it [09:37:55] * ChanServ sets mode: +o temporalfox

[12:37:48] * ChanServ sets mode: +o temporal_ [14:17:23] * ChanServ sets mode: +o temporalfox

[15:13:29] * ChanServ sets mode: +o temporalfox [16:54:08] * ChanServ sets mode: +o temporalfox

[19:12:04] * ChanServ sets mode: +o temporalfox [21:34:33] * ChanServ sets mode: +o temporalfox