[08:28:56] * ChanServ sets mode: +o temporalfox [08:59:33] <pmlopes> @h31 we've asked those results to be removed because (only json and plaintext are correct) because they branched the git reppo in a hurry for their round 12 while we were still adding the proper implementation with vertx-web. If you want better results you should run the benchmark yourself with the current git code, you will see that it performs as expected ;) [09:02:54] <pmlopes> @h31 also note that round 12 was a mess, just follow the thread: https://groups.google.com/forum/#!topic/framework-benchmarks/I2u3IU38uOM results to not match the logs, etc… etc… [10:33:14] * ChanServ sets mode: +o temporalfox
[11:01:03] <amr> how good is “as expected”? pmlopes
[11:04:37] <pmlopes> “as expected” means that it out performs non-reactive platforms. If you want real numbers you need to run the framework yourself, i don't have it the full results on my machine and setup and running the bechmark can take several days
[11:04:55] <s0x> hey guys, I've some trouble adjusting the log level of my vertx app. Chaning .LEVEL in vertx-default-jul-logging.properties effects the file-based logging even though I cannot see any effect on the console. In particular I wanna switch the console log level to debug (FINE)
[11:05:25] <amr> thanks :)
[11:09:04] <s0x> the vertx-default-jul-logging.properties looks as follows: http://pastebin.com/saKjcTSa
[11:18:32] <s0x> does anyone has a working logging properties file which includes the debug output?
[16:02:03] * ChanServ sets mode: +o temporalfox [16:07:32] * ChanServ sets mode: +o temporalfox
[17:17:38] <ChicagoJohn> can you use mocking in vertx to mock url responses?
[17:55:21] * ChanServ sets mode: +o temporalfox [18:11:06] * ChanServ sets mode: +o temporalfox