IRC Logs for #circuits Saturday, 2014-06-14

*** ircnotifier has quit IRC06:59
*** kdb_ has joined #circuits07:16
*** ircnotifier has joined #circuits07:18
kdb_Heya ircnotifier07:18
*** kdb_ has quit IRC09:28
*** Osso has joined #circuits10:56
*** Osso has quit IRC10:58
*** Romster has quit IRC11:52
*** Romster has joined #circuits11:52
*** Osso has joined #circuits13:12
*** Osso_ has joined #circuits13:43
*** Osso has quit IRC13:45
robert_Romster: how goes?14:12
*** Osso has joined #circuits14:56
Romsterrobert_, i'm going good15:07
robert_fun. :D15:07
*** Osso has quit IRC15:58
*** Osso has joined #circuits15:58
*** Osso has quit IRC17:40
*** Osso has joined #circuits17:40
*** Osso has quit IRC17:53
robert_hm, prologic- what happens if a component is busy doing something when it receives an event?19:21
*** Osso has joined #circuits19:50
*** Osso has quit IRC20:31
*** Osso has joined #circuits20:31
prologicrobert_, not possible21:08
prologicevent handlers will block the event loop21:08
prologicso don't do CPU bound work in them21:09
prologicuse the Worker() component21:09
prologicand fire task() events at it21:09
prologicevents are handled one at a time21:09
*** Osso has quit IRC21:23
*** Osso has joined #circuits21:24
robert_ah, okay.21:29
robert_prologic: got an example?21:29
prologicYou can also take advantage of circuits builtin coro/sync features and perform "work" inside an event handler iteratively21:51
*** Osso has quit IRC22:27

Generated by 2.11.0 by Marius Gedminas - find it at!