IRC Logs for #circuits Wednesday, 2018-11-28

*** patx has joined #circuits01:40
*** patx has quit IRC01:41
*** patx has joined #circuits01:41
patxis there anyplace available to view an example of the Worker component in action, i noticed it was mentioned in the circuits.web user manual in reference to interfacing with a database01:43
patxi found factorial example so looking at that02:24
*** patx has quit IRC02:25
*** prologic_ has joined #circuits09:03
*** ke4roh__ has quit IRC11:26
*** ke4roh__ has joined #circuits12:22
*** gdhvcvzpciwoxyvj has joined #circuits15:00
*** Workster has quit IRC15:00
*** ke4roh_ has joined #circuits15:59
*** ke4roh__ has quit IRC16:01
*** ke4roh__ has joined #circuits16:53
*** ke4roh_ has quit IRC16:55
spaceonehey prologic20:57
spaceonei want to try to implement some throttling for the IRC protocol component20:57
spaceonebecause if you send too much lines IRC servers usually disconnect you due to flooding20:57
spaceonei am not sure, how i will implement this. probably a new event, and wrap all PRIVMSG events i fire20:58
spaceonethis is not optimal but probably the fastest way to implemennt20:59
spaceoneas first draft for myself20:59
spaceonemaybe if anyone has a idea how to make this generic / (where)20:59
spaceonei can implement something for circuits directly20:59
*** ke4roh__ has quit IRC21:16
prologic_a generic component that listens for events on handlers that are decorated with "rate_limit"21:53
prologic_or "rate"21:53
prologic_with values like N/S where N is number and S is time interval21:54
prologic_then if the threshold is exceeded start dropping those events by filtering them out21:54
prologic_e.g: event.stop()21:54
prologic_or re-enqueue them up later21:54
spaceonesounds nice21:54
spaceonei currently think about implemented a yield sleep(); yield next_event()21:55

Generated by 2.14.0 by Marius Gedminas - find it at!