Differences

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

Link to this comparison view

irc:1463004000 [2017/05/27 13:44]
irc:1463004000 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[00:18:02] *** ChanServ sets mode: +o temporalfox
 +
 +[09:17:22] *** ChanServ sets mode: +o temporalfox
 +
 +[09:46:08] *** ChanServ sets mode: +o temporalfox
 +
 +[09:52:29] *** ChanServ sets mode: +o temporalfox
 +
 +[10:40:02] <​BadApe>​ say i have a json array of objects i want to write into a db, normally i would iterate over the array and write each row
 +
 +[10:41:05] <​BadApe>​ but i have an async handler that writes a record now, i need someway to block the loop or not use a loop at all?
 +
 +[11:54:36] <​temporalfox>​ BadApe with 3.3 you can use batching I think for this
 +
 +[12:11:43] <​BadApe>​ good to know, thanks temporalfox
 +
 +[12:11:50] <​BadApe>​ what is the ETA for 3.3 ?
 +
 +[14:20:13] <​amack2>​ Hi, I have a publisher, writing to an address, and two consumers on this address. Published message are only seen by one consumer, in a round-robin fashion. I thought all message should be seen by all consumers. Am I missing something? I'm on 3.2.1
 +
 +[14:39:49] <​amack2>​ Sorry, my mistake: Two producers sending to the same address results in round-robin
 +
 +[14:40:16] <​amack2>​ eb.publish from two different verticales results in the expected behavior
 +
 +[14:41:32] <​AlexLehm>​ BadApe: you can simulate a loop with an async call by iterating the counter and call the same method with c+1 in the result handler of the previous call
 +
 +[17:17:38] <​skullcrasher>​ how do I wait in a REST api call (e.g. with spring) for the results of a vertx handler?
 +
 +[18:03:15] *** ChanServ sets mode: +o temporalfox
 +
 +[19:14:38] *** ChanServ sets mode: +o temporalfox
 +
 +[19:48:45] *** ChanServ sets mode: +o temporalfox
 +
 +[20:06:53] *** ChanServ sets mode: +o temporalfox
 +
 +[20:35:31] *** ChanServ sets mode: +o temporalfox
 +
 +[22:19:33] *** ChanServ sets mode: +o temporalfox