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

[00:52:12] * ChanServ sets mode: +o temporalfox [01:13:25] <kjar> are there any good references / examples of Future.compose out there? I have a sequence of HTTP client requests where the response of one is needed to make the next one, and am looking for a better way than nesting setHandlers. [01:17:28] <Sticky> kjar: not sure about future compose, but I have used rx's and-then-when to do this [01:18:00] <Sticky> basicly you can say “go do all these things, then notify me of the results when they are all in” [01:19:35] <Sticky> hmm, actually rxjavas flatmap may be more what you are after [01:19:38] <kjar> my use-case is one of consecutive dependency, request 2 depends on response of request 1, and so on [01:19:58] <Sticky> yeah, flatmap is what you want I believe [01:20:54] <Sticky> assuming you want to use rx that is [01:23:06] <Sticky> does look like thencompose as you said should do what you want [01:23:46] <Sticky> hmm, I should use this more [04:08:37] <voidDotClass> Is it possible to accept / send DTLS/SRTP packets / connections on the server using vertx? [08:34:12] * ChanServ sets mode: +o temporalfox

[08:51:25] <DwJ> Hi All, I am very new to vert.x, Just 10 mins ago I came to know about it, any help on where to start learning

[08:51:42] <DwJ> looked at

[08:52:16] <DwJ> trying out the

[08:52:29] <cescoffier> DwJ : Hi, yes that's a good start

[08:52:30] <DwJ> any book recommendation?

[08:52:51] <cescoffier> we don't have a “book” per se, but we have an extended lab (~ 60 pages)

[08:52:57] <cescoffier>

[08:53:08] <cescoffier> (and freshly updated this morning)

[08:54:17] <cescoffier> there are also a couple of video from different conferences giving a good introduction to vert.x

[08:54:37] <cescoffier> check here:

[08:55:50] <pmlopes> and don't forget the youtube channel with lots of presentations:

[10:41:22] <DwJ> Thank a lot cescoffier !! Seems like a gold mine of vertx :)

[10:41:42] <cescoffier> you're welcome !

[15:29:54] <kjar> I'm seeing an odd DNS lookup issue with the http client: It fails to resolve (only) a certain domain after 3 tries, while Curl has no such issue. Could anyone shed some light on why that might be?

[16:23:19] <seemsindie> hello just one quick question, how do i read data from jwt token? how would i get “sub” form token in protected route?

[16:24:30] <pmlopes> @seemsindie the auth user is your token

[16:26:06] <pmlopes> ctx.user().principal() is a json object with the decoded token value

[16:26:48] <seemsindie> @pmlopes I am sorry just picked vert.x from nodejs, still new in all of this. I didn't see there is auth-common, i'll read this first.

[16:27:01] <seemsindie> @pmlopes thanks :)

[16:52:48] <pmlopes> no problem!

[19:17:34] <closed_socket> I am trying to build a small project using the vertx-codegen. It creates the *.groovy files, however I am unable to package them into the created jar. The jar seems to include the js and the java implementations, however the compiled groovy files are missing. The target directory also does not seem include the compiled groovy files. Is there an example where I can have a look at how I need to configure the pom.xml correctly?

[19:32:33] <closed_socket> ah, just found the vertx-ext-parent artifact, I think I got it working now…

[19:43:17] <AlexLehm> closed_socket: this should be an example

[19:45:14] <closed_socket> AlexLehm: Great. Thank you. Another question. My Interface extends other third party interfaces, which obviously do not have the @VertxGen annotation. I just noticed these interfaces get removed in the generated groovy class. Is there anything I can do to keep the third party interfaces?

[19:46:48] <AlexLehm> I don't think the generation works for subinterfaces, you might want to ask that temporalfox though

[19:51:03] <closed_socket> AlexLehm: Yes, from what the docs say I don't think it is possible. I guess it will be easier to just add the groovy src in that case

[19:59:47] <kjar> anyone here familiar with DNS resolution with http client? I'm having an issue where resolution fails for a domain that resolves multiple times before getting to an IP.

[20:00:43] <kjar> when I iterate with a DnsClient 3 times I finally get to an IP, however I get DNS resolution failure when using the http client directly

[20:10:23] <AlexLehm> the http client uses the dns resolution from netty, i think it does multiple tries

[20:11:07] <kjar> AlexLehm: I figured, http client use DnsClient usess netty, but I haven't checked the code yet

[20:11:38] <kjar> I suspect no one try is failing, just that it's not “digging” down

[20:11:58] <AlexLehm> does this happen if you use the dns client in vertx directly?

[20:12:45] <kjar> I have used DnsClient.lookup4 on the domain in question, it resolves to another domain, apply DnsClient.lookup4 on that domain, resolves to yet another, and finally that last one resolves to an IP. so that works

[20:14:54] <kjar> I would share the domain in question for independent testing, however it is somewhat secret unfortunately

[20:54:56] <kjar> AlexLehm: for the record, increasing the max queries address resolver option from 3 to 7 made my query work

[21:16:38] <AlexLehm> kjar: ah, that is due to the number of CNAMES I assume

[21:17:03] <AlexLehm> maybe it is possible to configure the query depth in the dns client

[21:19:01] <kjar> VertxOptions opts = new VertxOptions(); opts.getAddressResolverOptions().setMaxQueries(8); Vertx vertx = Vertx.vertx(opts);

[21:19:21] <kjar> AlexLehm: that worked for me, is that what you meant?

[21:20:19] <AlexLehm> yes, i think this is passed to the netty resolver

[21:57:08] *** ChanServ sets mode: +o temporal_