Differences

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

Link to this comparison view

irc:1452380400 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[00:45:15] *** ChanServ sets mode: +o temporalfox
 +
 +[03:10:49] *** ChanServ sets mode: +o temporal_
 +
 +[05:18:20] <​bosyak_>​ If single Verticle consume messages on two different "​channels"​ is it possible that two messages will arrive on same time?
 +
 +[08:56:56] *** ChanServ sets mode: +o purplefox
 +
 +[12:08:21] <​Sticky_>​ bosyak: a verticle is in effect single threaded, so two things can never happen at the same time within a verticle
 +
 +[14:48:29] <​bosyak>​ Sticky_, are you sure? I'm just want to be sure about you :)
 +
 +[15:32:19] <​AlexLehm>​ bosyak:
 +
 +[15:32:57] <​AlexLehm>​ bosyak: a normal verticle runs in a single thread so that it will not have anything happening at the same time, rather the handlers get called after each other
 +
 +[15:33:49] <​bosyak>​ AlexLehm, if my Verticle is worker?
 +
 +[15:34:11] <​AlexLehm>​ if the verticle is worker, it is running in a worker thread, then you have to consider thread safety
 +
 +[15:34:58] <​AlexLehm>​ if you are in a single worker verticle, the single thread thing applies as well I think
 +
 +[15:35:52] <​bosyak>​ ok, thanks. I think I should test it somehow
 +
 +[15:42:29] <​AlexLehm>​ if you add the thread id to your logger, it should work nicely to check which part of the code is executed with which thread
 +
 +[15:44:51] <​bosyak>​ AlexLehm, nice idea! :) Vertx add thread'​s name by it self
 +
 +[15:49:02] <​bosyak>​ I rewrote my pet application with Vertx... ​ And I like it :) EventBus is perfect pattern. Later I'll check how its working in distributed enviroment. Anyway I like it.
 +
 +[19:32:13] *** ChanServ sets mode: +o purplefox
 +
 +[20:25:53] *** ChanServ sets mode: +o temporalfox
 +
 +[21:13:39] *** ChanServ sets mode: +o temporalfox
 +
 +[22:58:51] *** ChanServ sets mode: +o temporalfox