[Python-ideas] The async API of the future: Twisted and Deferreds
shane at umbrellacode.com
Mon Oct 15 03:50:56 CEST 2012
Okay, I hate to do this, but is there any chance someone can provide a quick summary of the solution we're referring to here? I just started watching python-ideas today, and have a lot of things going on, plus real bad ADD, so I'm having a hard time reassembling the solutions being referred to… (maybe there's a web presentation that gives a better threaded presentation than my mail program? Or maybe I'm daff. Either way, this sounded interesting!)
In summary, then, the Q/A below is referring to which approach?
805-452-9666 | shane at umbrellacode.com
On Oct 14, 2012, at 5:23 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> Guido van Rossum wrote:
>> The thing that worries me most is reimplementing httplib, urllib and
>> so on to use all this new machinery *and* keep the old synchronous
>> APIs working *even* if some code is written using the old style and
>> some other code wants to use the new style.
> I think this could be handled the same way you alluded to
> before when talking about the App Engine. The base implementation
> is asynchronous, and you provide a synchronous API that sets
> up an async operation and then runs a nested event loop until
> it completes.
> Python-ideas mailing list
> Python-ideas at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas