*** koobs has quit IRC | 01:59 | |
*** koobs has joined #circuits | 02:01 | |
*** koobs has quit IRC | 03:06 | |
*** koobs has joined #circuits | 03:07 | |
*** koobs has quit IRC | 03:34 | |
*** koobs has joined #circuits | 03:35 | |
spaceone | circuits.web has no date parsing at all | 08:11 |
---|---|---|
spaceone | prologic: is it okay to change the channel of a running component? | 10:36 |
*** Workster has quit IRC | 15:20 | |
*** linkedinyou has quit IRC | 15:43 | |
*** linkedinyou has joined #circuits | 15:46 | |
prologic | spaceone: it's okay yes | 16:04 |
prologic | I think :) | 16:04 |
prologic | -but- I'm not sure it marks the handler cache as dirty though | 16:04 |
prologic | you'd have to do that by hand | 16:04 |
prologic | maybe we should make doing something like this from a public API possible and more clear? | 16:04 |
prologic | like make Component.channel a mutable property such that mutating it during runtime will mark the internal handler cache of the root manager dirty and recalculate all handlers | 16:05 |
spaceone | prologic: it's useful if i want that the read event of a socket is not anymore handlded by a specific component because i change the protocol | 16:08 |
prologic | *nods* | 16:50 |
prologic | there are probably other useful use-cases too | 16:50 |
prologic | it's not that common; but I think we should support this | 16:51 |
*** linkedinyou has quit IRC | 20:10 | |
*** Workster has joined #circuits | 22:08 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!