IRC Logs for #circuits Thursday, 2014-10-16

*** robert_|disconne has quit IRC02:02
*** robert_|disconne has joined #circuits02:02
*** tariq786 has joined #circuits07:14
*** tariq786 has quit IRC09:09
*** tariq786 has joined #circuits09:17
*** tariq786 has quit IRC09:23
*** koobs has quit IRC09:32
*** koobs has joined #circuits09:32
*** koobs has quit IRC09:40
*** techdragon has quit IRC09:55
*** techdragon has joined #circuits10:00
prologichello techdragon10:04
*** koobs has joined #circuits10:06
*** koobs has quit IRC10:20
*** koobs has joined #circuits10:51
*** koobs has quit IRC11:04
*** koobs has joined #circuits11:30
*** cfarmer has joined #circuits18:06
*** koobs has quit IRC18:28
*** koobs has joined #circuits18:29
*** sapiosexual has quit IRC19:00
*** sapiosexual has joined #circuits19:01
*** tariq786 has joined #circuits20:02
prologicmorn’n all23:28
robert_prologic: can you listen to more than one event channels without manually ignoring events, or is that the way to listen to then? lol23:37
prologicwhy would you want to listen to channels?23:40
prologicchannels != events23:40
prologicthey are used merely as seaprateres of potentialyl conflicting events23:40
prologici.e: separation of concerns23:40
prologicfor say two read events that need to be treated differently23:40
robert_well, I have two channels that I want to listen to for core events; namely the MainApplication and the Scheduler components.23:40
prologicor e.g: two server components that treat each incoming connection differently23:40
prologicwell is it possible to setup an event handler for a given event or set of events23:41
prologicand set the channel to *23:41
prologice.g: @handler(“foo”, “bar”, channel=“*")23:41
robert_oh, yeah. like you do.23:41
prologicbut listening to multiple channels has not made sense and/or we’ve not found a use-case for such a feature23:42
prologicdefinately listening for multiple events - yes :)23:42

Generated by 2.11.0 by Marius Gedminas - find it at!