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

[04:16:00] <wayne_> hi ,do you know how to set the cluster name ?

[06:38:44] <Mukarr> I have shared draft of my proposal for the project Implementation of blueprint applications along with the link to the completed proposal task for the same.

[06:39:10] <Mukarr> Please review and suggest changes or improvements.

[08:01:33] *** ChanServ sets mode: +o temporal_

[11:51:14] <AshwinSurana> Hello! I have shared my draft proposal for Implementation of “blueprint” application, please review and let me know for changes or improvements

[17:14:11] <jerrinot> Hi, I'm trying to get some feedback on a possible improvement in vert.x - Hazelcast integration: the goal is remove reliance on the executeBlocking(). it's outlined at https://github.com/vert-x3/vertx-hazelcast/issues/28

[17:14:19] <jerrinot> I appreciate any kind of feedback!

[17:21:39] <cescoffier> jerrinot : Hi !

[17:22:00] <cescoffier> Sorry, it left my radar, I just commented on it

[17:22:12] <jerrinot> great, much appreciated!

[17:23:03] <cescoffier> so, my only issue is loosing compatibility with HZ 3.4 and 3.5. Do you know when this async api has been added ?

[17:27:03] <jerrinot> let me check it

[17:28:24] <cescoffier> jerrinot : can you tell me what's the VertxExecutorAdapter ? We don't have this right now

[17:28:43] <cescoffier> is is a kind of ExecutorService that execute the submitted task in the right context ?

[17:29:27] <jerrinot> async API is relatively old. However older versions are known to have issues. Perhaps we could use the new non-blocking implementation only when a sufficiently recent Hazelcast is detected?

[17:31:24] <jerrinot> sure, when ICompletableFuture is completed then its callbacks are executed by a thread from one of the Hazelcast threadpool by default. You can supply your own Executor you want to use to execute the

[17:31:35] <jerrinot> sure, when ICompletableFuture is completed then its callbacks are executed by a thread from one of the Hazelcast threadpool by default. You can supply your own Executor you want to use to execute the the callback

[17:33:32] <jerrinot> I am not a vert.x expert at all, but I assume the callback has to be executed by one of the vert.x threads.

[18:03:09] <cescoffier> when the completable future is completed, the callback should be called in the context thread

[18:03:34] <cescoffier> so, that would not be an executor, but more a context.runOnContext()

[19:39:28] <pnutbutr> When I run a code block in vertx.executeBlocking(), does that block the event loop? Or does that spawn a worker thread to handle that code chunk?

[19:39:42] <pnutbutr> apologies if that's a misguided question. I'm learning the vertx/async ropes.

[20:34:26] <kuwv> I'm curious about jython in vertx. Can anyone answer some questions qbout it?