| *** green1 has joined #circuits | 00:06 | |
| *** ablest1980 has joined #circuits | 00:44 | |
| *** ablest1980 has quit IRC | 00:46 | |
| *** ablest1980 has joined #circuits | 00:47 | |
| *** ablest1980 has quit IRC | 00:49 | |
| *** ablest1980 has joined #circuits | 00:53 | |
| *** ablest1980 has quit IRC | 00:53 | |
| *** ablest1980 has joined #circuits | 00:53 | |
| *** ablest1980 has quit IRC | 00:55 | |
| *** ablest1980 has joined #circuits | 00:55 | |
| *** ablest1980 has quit IRC | 01:06 | |
| *** ablest1980 has joined #circuits | 01:07 | |
| *** ablest1980 has quit IRC | 01:24 | |
| *** ablest1980 has joined #circuits | 01:26 | |
| *** ablest1980 has quit IRC | 01:40 | |
| *** edk has quit IRC | 02:32 | |
| *** edk has joined #circuits | 02:34 | |
| *** green1 has quit IRC | 03:34 | |
| *** Osso has joined #circuits | 08:38 | |
| *** Osso has quit IRC | 10:07 | |
| *** Osso has joined #circuits | 10:09 | |
| *** Romster has quit IRC | 14:16 | |
| *** Romster has joined #circuits | 14:22 | |
| *** ninkotech has quit IRC | 14:27 | |
| *** ninkotech has joined #circuits | 14:39 | |
| riot | i'm writing a database backend and am wondering: what is the best way to fetch and store database data with circuits? I'll have ~10-20 clients writing and reading a lot of mongodb stored stuff. should i actually do this via events? | 15:42 |
|---|---|---|
| riot | then i'd have to store state and await the response, isn't there a better way? | 15:43 |
| *** Osso_ has joined #circuits | 17:14 | |
| *** Osso has quit IRC | 17:14 | |
| *** ablest1980 has joined #circuits | 18:10 | |
| *** ablest1980 has quit IRC | 18:22 | |
| *** Zimsky has quit IRC | 18:34 | |
| *** green1 has joined #circuits | 18:55 | |
| *** Zimsky has joined #circuits | 19:21 | |
| prologic | riot, use a thread pool :) | 20:02 |
| prologic | async db stuff is hard | 20:02 |
| prologic | a lot of dbs don't do async very well | 20:02 |
| riot | prologic: hm, i don't think so: http://css.dzone.com/articles/requests-python-and-mongodb | 20:36 |
| riot | but, yeah, threadpool, it seems to be | 20:36 |
| riot | but then, how do i get data from components to the database component and vice versa? | 20:40 |
| *** Osso has joined #circuits | 20:59 | |
| *** Osso has quit IRC | 21:04 | |
| prologic | riot: coroutines :) | 21:34 |
| prologic | you know... that yield/call/wait stuff in circuits :) | 21:34 |
| prologic | haha | 21:34 |
| prologic | you can also have a threaded Worker pool | 21:34 |
| prologic | Worker().register(...) | 21:35 |
| prologic | by default unless you pass process=True | 21:35 |
| prologic | the Worker is a threadpool | 21:35 |
| prologic | wrapping around multiprocessing.pool.ThreadPool | 21:35 |
| prologic | riot: of course... it would be nice if someone ported or added support for circuits wrt async mongodb support | 21:40 |
| prologic | if you have a look at motor | 21:40 |
| prologic | maybe that can be ported to circuits | 21:40 |
| prologic | or support added | 21:40 |
| prologic | be nice :) | 21:40 |
| *** ablest1980 has joined #circuits | 21:45 | |
| *** ablest1980 has quit IRC | 21:47 | |
| *** green1 has quit IRC | 21:50 | |
| *** green1 has joined #circuits | 21:51 | |
| *** Osso has joined #circuits | 22:56 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!