[12:21:34] <dpes> andyhedges: i know… I've asked not only about this thing… i think i will be using vertx for some long distance project so i will be using docs a lot and want to know how to contribute things like that

[12:21:46] <andyhedges> Fair enough :)

[12:21:48] <dpes> now i know

[12:22:19] <andyhedges> AlexLehm: awesome, is it in the snapshot yet do you know?

[12:23:04] <AlexLehm> i think the snapshot is build on the jenkins, so it should be in the snapshot

[15:27:36] <AlexLehm> can i merge commits with comment changes only directly or should i a pr for that

[18:12:40] <AlexLehm> purplefox, can i merge commits with comment changes only directly or should i a do pr for that

[21:13:59] <Terabyte> hey

[21:14:44] <Terabyte> suppose you've written a web app in vertx, request comes in, you put an event to the event bus saying “take this action”, the action requires a response. how does vertx correlate a response back to the original request and send the response back to the user?

[22:29:17] <AlexLehm> Terabyte, you have to send the response back to the user in the handler that receives the response from the bus

[22:30:12] <AlexLehm> the handler has the objects of the user request/response in its method body available

[23:31:02] <Terabyte> AlexLehm thanks, still not clear though, how the result of some async operation happening over a bus can be matched up with the request that triggered it..

[23:31:54] <Terabyte> does the eventbus just 'handle' that?

[23:37:17] <AlexLehm> i assume the event bus has some kind of request id that is returned in the response