Differences

This shows you the differences between two versions of the page.

Link to this comparison view

irc:1466028000 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[00:00:09] <​temporalfox>​ cool
 +
 +[00:00:14] <​temporalfox>​ need to go, ttyl!
 +
 +[07:50:26] *** ChanServ sets mode: +o temporalfox
 +
 +[09:19:09] *** ChanServ sets mode: +o temporalfox
 +
 +[11:39:59] *** ChanServ sets mode: +o temporalfox
 +
 +[13:36:31] *** ChanServ sets mode: +o temporalfox
 +
 +[14:00:35] <​AlexLehm>​ temporalfox:​ do you want to review the pr for the mail issue? the change in main/src is very small
 +
 +[14:01:05] <​temporalfox>​ n/p
 +
 +[14:01:06] <​temporalfox>​ has the pr been done ?
 +
 +[14:01:17] <​AlexLehm>​ i have put up the pr yesterday evening
 +
 +[14:01:29] <​AlexLehm>​ https://​github.com/​vert-x3/​vertx-mail-client/​pull/​73
 +
 +[14:07:51] <​temporalfox>​ ok
 +
 +[14:07:52] <​temporalfox>​ my internet is really bad
 +
 +[14:07:54] <​temporalfox>​ well my connection to the internet :-)
 +
 +[14:16:00] <​AlexLehm>​ temporalfox:​ i can merge the pr tonight if its ok for you
 +
 +[14:16:24] <​temporalfox>​ it's ok
 +
 +[14:16:29] <​temporalfox>​ merge whenver you prefer
 +
 +[14:16:42] <​AlexLehm>​ ok, thanks
 +
 +[14:36:57] <​baris>​ Hi there
 +
 +[14:37:39] <​baris>​ I have a question on vertx. Is it ok to ask here?
 +
 +[14:41:23] <​baris>​ QUESTION: Is it possible to find a specific verticle (by using its deploymentId or sth else) )on Vertx cluster?
 +
 +[14:43:49] <​moment-4>​ yes, vertx-shell?​ or do you mean programmatically?​
 +
 +[14:45:15] <​baris>​ programmatically
 +
 +[14:45:17] <​baris>​ Java
 +
 +[14:47:20] <​baris>​ Actually what I want achieve is reacing specific verticle and call a method belongs that verticle. @moment-4
 +
 +[14:47:56] <​moment-4>​ vertx.deploymentIds()
 +
 +[14:48:22] <​moment-4>​ Return a Set of deployment IDs for the currently deployed deploymentIDs.
 +
 +[14:48:59] <​moment-4>​ hmmm, I don't really get the point of what you're trying to achieve... there'​s the eventbus to communicate between verticles. (That'​s the whole point of verticles :) ).
 +
 +[14:49:24] <​moment-4>​ Anyway, I have to go... sorry, if nobody else can help you out, I'm here tomorrow morning (CEST)
 +
 +[14:59:14] <​nicovanbelle>​ Hi! I was wandering how one can use CompositeFuture.all in combination with HttpClientRequest objects (or http requests in general)
 +
 +[15:00:16] *** ChanServ sets mode: +o temporalfox
 +
 +[15:35:46] *** ChanServ sets mode: +o temporalfox
 +
 +[15:57:15] *** ChanServ sets mode: +o temporalfox
 +
 +[16:28:41] *** ChanServ sets mode: +o temporalfox
 +
 +[17:53:55] <​robal>​ hi guys, I've hit a wall... with Vertx3 i'm writing an integration test with POST parameters.
 +
 +[17:54:40] <​robal>​ I've found an example with vertx2 and a test suite, however I can't seem to rewrite this to a working Vertx3 format
 +
 +[17:55:41] <​robal>​ so, if anyone has a working Vertx3 unit test with POST parameters please give me a head up
 +
 +[18:01:04] <​robal>​ something like this works great for a GET request, but im not sure how to pass a POST body
 +
 +[18:01:24] <​robal>​ vertx.createHttpClient().getNow(port,​ "​localhost",​ "/​robots.txt",​ response ->
 +
 +[18:16:27] <​robal>​ ahhhh nice... I figured it out!
 +
 +[19:03:11] <​nicovanbelle>​ Hi! I was wandering how one can use CompositeFuture.all in combination with HttpClientRequest objects (or http requests in general)
 +
 +[19:10:25] <​nicovanbelle>​ guess this is not a good place to ask questions