IRC Logs for #circuits Saturday, 2014-11-15

*** Osso has quit IRC01:09
*** Osso has joined #circuits01:09
*** LyndsySimon has joined #circuits18:23
LyndsySimonprologic: OK, I'm more than intrigued now by circuits. I'm going to build some proof-of-concept stuff to better learn how it will effect my development process.18:24
LyndsySimonCould you point me to an example of properly using a database in a non-blocking way?18:25
LyndsySimonI normally prefer traditional SQL databases, but I'm fairly experienced with MongoDB and would like to use whatever is best suited for the event-driven style of circuits.18:26
LyndsySimonIn short - teach me, sensei :)18:26
pdurbinLyndsySimon: I think it's 4:30 in the morning for prologic18:32
LyndsySimonNot a problem - I expected that communications dealing with circuits would be asynchronous and non-blocking...18:35
pdurbin:)18:36
*** irclogger_____ has quit IRC18:58
*** irclogger______ has joined #circuits18:58
*** LyndsySimon has quit IRC19:00
*** y0noz has joined #circuits19:01
*** pdurbin has quit IRC19:05
*** LyndsySimon has joined #circuits19:09
*** pdurbin has joined #circuits19:09
*** pdurbin1 has joined #circuits19:41
*** pdurbin has quit IRC19:47
*** An_Ony_M1ose has joined #circuits20:00
*** An_Ony_Moose has quit IRC20:05
*** pdurbin1 has quit IRC20:09
*** An_Ony_M1ose has quit IRC20:10
*** An_Ony_Moose has joined #circuits20:10
*** borntyping has quit IRC20:11
*** borntyping has joined #circuits20:12
*** pdurbin1 has joined #circuits20:22
*** koobs has quit IRC20:50
*** koobs has joined #circuits22:11
prologichey LyndsySimon22:44
prologicsorry for the delay22:44
prologictimezone differences :)22:44
prologiclol22:45
prologicokay just read the backlog22:45
prologicregarding database stuff and async22:46
prologicunfortunately as you're probably very much aware many databases do not support async operations very well (if at all)22:46
prologicmost db(s) leave you with one option to run operations in a thread22:46
prologicanyway22:47
prologicwe don't (unfortunately) have any nice db wrappers as such, I've not written any, nor has anyone else :) so I assume folks just use threading and/or the circuits Worker component (which wraps around multiprocessing)22:48
prologice.g:22:48
prologicsomewhere in your app'a stack22:49
prologicfrom circuits import Worker22:49
prologicWorker().register(app)22:49
prologic...22:49
prologicsomewhere you might do db stuff22:49
prologicfrom circuits import task22:49
prologicyield self.call(task(save_data, "Bob", 1234), "worker))22:50
prologicin practice it would not be that hard to integrate some kind of db through SA, mongoengine, or plain ol db-api22:51
prologichttps://bitbucket.org/prologic/autodock/src/ad0b3eb4ee1c33c16cfab21b704d7fdea22c37b5/autodock/main.py?at=default#cl-2922:51
prologicI know this isn't a database -- but this is how I integrate a blocking process from the docker-py library's Client.events()22:52
prologicLyndsySimon, just found the one project where I have used a db before :)22:58
prologichttps://bitbucket.org/prologic/sahriswiki/src/f0102ce480ccaf7c1dc29c92202b9153894f6b86/sahriswiki/dbm.py?at=default22:58
prologichttps://bitbucket.org/prologic/sahriswiki/src/f0102ce480ccaf7c1dc29c92202b9153894f6b86/sahriswiki/search.py?at=default23:01
prologicessentially I just let SQLAlchemy handle it (it uses a thread pool)23:01

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!