I’ve mentioned this on an issue in txdbus https://github.com/cocagne/txdbus/issues/11 and the author had some pretty good points on implementing a twisted/asyncio abstraction
in the txdbus library. I would be willing to contribute to this as well if the decision is taken to simply work on top of txdbus. On Wed, May 20, 2015 at 5:01 AM, Elizaveta Guseva <[email protected]> wrote: > Hello Pontus, > Oh, cool! Thanks a lot for your recommendation! > I will definitely look into it. > Eliza > On Tue, May 19, 2015 at 7:47 AM, Pontus Karlsson < > [email protected]> wrote: >> Not sure on how far you've gotten on researching this, but as the model of >> asyncio is heavily inspired by the Twisted structure >> I would recommend trying to port txdbus >> <https://github.com/cocagne/txdbus> to asyncio. >> >> I was actually looking into doing this a month back and started to map the >> code structure and looking into what needs to be altered: >> >> - *authentication.py* - Zope interfaces, twisted logger >> - *bus.py* - twisted logger and Factory? >> - *client.py* - Heavy twisted usage >> - *endpoints.py* - Heavy twisted usage >> - error.py - No Twisted API usage >> - interface.py - No Twisted API usage >> - introspection.py - No Twisted API usage >> - marshal.py - No Twisted API usage >> - message.py - No Twisted API usage >> - *objects.py* - Zope interfaces, twisted defer >> - *protocol.py* - Zope interfaces, heavy twisted usage >> - *router.py* - Twisted log >> >> My recommended approach here is to fork it and abstract the event loop to >> work with both Twisted and asyncio. >> >> Den måndag 4 maj 2015 kl. 22:54:20 UTC+2 skrev Eliza Guseva: >>> >>> Hello all, >>> >>> First. Thanks a lot for choosing me as a student for your project!! >>> >>> As an international student in USA, I'm having some challenges with >>> bureaucratic system in my University. >>> It starts taking too long at the moment. So I'd better not wait even >>> longer and start communication now. >>> I have to warn: there might be issues with the system, but I'm trying >>> hard to get it work. >>> >>> On the brighter topic:) >>> As I understand it's time to read the documentation now. >>> Could you recommend me the reading, which suits the best for the purposes >>> of the project? >>> What source codes do you think, I should look into to get a better >>> understanding? >>> I will be asking questions, in the progress. >>> >>> Thanks a lot! >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "qtile-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the Google > Groups "qtile-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qtile-dev/eica8sXohwI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qtile-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
