Differences

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

Link to this comparison view

irc:1472508000 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[01:23:21] <​alphahelix>​ Hi there, if anyone is willing to help, how I could set up a registration service with JDBC Auth (database storing user info is Postgres)?
 +
 +[12:51:20] <​AlexLehm>​ temporalfox:​ netty 4.1.5 was released yesterday, could you include that in vertx and apply for the eclipse clearance (or what its called)?
 +
 +[13:09:33] <​temporalfox>​ AlexLehm yes I should
 +
 +[13:09:42] <​temporalfox>​ however that would delay Vert.x 3.3.3 release
 +
 +[13:09:46] <​temporalfox>​ what are the noticeable fixes ?
 +
 +[13:11:58] <​temporalfox>​ there are quite some fixes, however I don't see anything outstanding
 +
 +[13:12:03] <​AlexLehm>​ there was one fix about ipv4/ipv6 that was reported in vertx by somebody using google compute cloud
 +
 +[13:12:04] <​temporalfox>​ I mean that would be blocker
 +
 +[13:12:06] <​temporalfox>​ yes
 +
 +[13:12:22] <​temporalfox>​ I'll file the eclipse cq now
 +
 +[13:12:33] <​temporalfox>​ it uses also new tc-native
 +
 +[13:13:15] <​AlexLehm>​ https://​github.com/​eclipse/​vert.x/​issues/​1570
 +
 +[13:13:23] <​AlexLehm>​ that is kind of a blocking issue
 +
 +[13:13:54] <​AlexLehm>​ https://​github.com/​netty/​netty/​issues/​5657
 +
 +[13:14:40] <​AlexLehm>​ the other stuff i fixed is in 4.1.4 already
 +
 +[13:21:48] <​temporalfox>​ AlexLehm so I mean not as outstanding as broken DNS resolving with search domains :-)
 +
 +[13:22:20] <​temporalfox>​ also user I think can upgrade netty version and override vertx'​s one
 +
 +[13:23:13] <​temporalfox>​ I sent an email on vertx-dev
 +
 +[15:48:03] <​AlexLehm>​ temporalfox:​ about the requestbuilder?​
 +
 +[15:48:14] <​temporalfox>​ AlexLehm hi I'm in meeting now
 +
 +[15:48:20] <​temporalfox>​ I'll ping you when I'm available
 +
 +[15:48:51] <​AlexLehm>​ ok
 +
 +[16:57:11] <​temporalfox>​ hi AlexLehm I'm available now :-)
 +
 +[17:03:11] <​AlexLehm>​ temporalfox:​ you said earlier that you sent an email on vertx-dev, i am not sure for which topic
 +
 +[17:03:28] <​temporalfox>​ about netty version
 +
 +[17:03:34] <​temporalfox>​ I replied to myself :-)
 +
 +[17:03:43] <​temporalfox>​ we can upgrade
 +
 +[17:04:43] <​AlexLehm>​ ok, what is your planned date for the 3.3.3 release?
 +
 +[17:06:06] <​AlexLehm>​ i can do some testing before since i am on vacation this week (at home)
 +
 +[17:07:08] <​AlexLehm>​ that should say before release
 +
 +[17:07:28] <​temporalfox>​ next week
 +
 +[17:07:48] <​AlexLehm>​ ok great
 +
 +[17:18:56] <​temporalfox>​ is everything fine on mail client side AlexLehm ?
 +
 +[18:37:36] <​AlexLehm>​ temporalfox:​ yes, that is ok
 +
 +[21:37:13] <​myghty>​ hey guys :)
 +
 +[21:37:26] <​myghty>​ I asked before but maybe now someone might be here to help
 +
 +[21:37:45] <​myghty>​ I am building a small microservice network which should be reachable via HTTP Restful Interface
 +
 +[21:38:08] <​myghty>​ so the idea right now is, that I have a single point of entry verticle
 +
 +[21:38:12] <​myghty>​ which then forwards the http requests to the corresponding other microservices
 +
 +[21:38:37] <​myghty>​ now I think there are two options, either use service proxies, or just make the others listeting for http requests...
 +
 +[23:40:23] <​temporalfox>​ myghty if you are doing vertx only, service proxy is a good choice