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

[15:02:03] * ChanServ sets mode: +o temporalfox [15:08:51] * ChanServ sets mode: +o temporalfox

[16:20:56] * ChanServ sets mode: +o temporalfox [16:59:36] * ChanServ sets mode: +o temporalfox

[17:06:34] * ChanServ sets mode: +o temporalfox [17:34:26] * ChanServ sets mode: +o temporalfox

[18:14:44] <Sticky> would there be any interest in making the eventbus created via a factory. I want to create an eventbus for debugging that will log everything that goes through it. Essentialy a more verbose metrics that could allow full post mortem of an app

[18:15:40] <Sticky> obviously using such an event bus permanently could be a performance issue, but can substitute it just for tests

[18:16:45] <Sticky> unfortunatly subbing out the event bus is difficult as its creation is embedded in VertxImpl, so I was just wondering if there was any scope for doing it via injection/factory

[18:20:50] * ChanServ sets mode: +o temporalfox [18:35:24] * ChanServ sets mode: +o temporalfox

[19:34:21] <kuwv> Anyone can help me with ruby questions?

[22:46:53] <AlexLehm> Sticky: have you tried to mock the vertx stuff with a partial mock?

[22:51:25] <Sticky> I presume you mean partial mocking VertxImpl and changing how it creates the EventBusImpl?

[22:51:44] <Sticky> should work I guess

[22:52:41] <Sticky> I was considering AOP to just “instrument” the EventBusImpl without modifying the class

[22:53:07] <Sticky> or Byteman

[22:54:04] <Sticky> but thought maybe vertx should be a bit more flexible to switching out event buses

[23:50:26] <AlexLehm> the eventbus is created in a private method in vertximpl, that is probably not changable without mocking or bytecode modification

[23:50:39] <AlexLehm> AOP might be a workable thing though