GET /api/v2/video/396
HTTP 200 OK Vary: Accept Content-Type: text/html; charset=utf-8 Allow: GET, PUT, PATCH, HEAD, OPTIONS
{ "category": "PyCon US 2011", "language": "English", "slug": "pycon-2011--an-outsider--39-s-look-at-co-routines", "speakers": [ "Peter Portante" ], "tags": [ "concurrence", "coroutines", "gevent", "greenlets", "pycon", "pycon2011" ], "id": 396, "state": 1, "title": "An outsider's look at co-routines.", "summary": "", "description": "An outsider's look at co-routines.\n\nPresented by Peter Portante\n\nLet's take an outsiders look at coroutines, the underlying concept used by\ngreenlets. First we'll define what they are conceptually, and show some\ntypical use cases. Then we'll take a look at a sampling of the implementations\nout there to see what they are actually doing to implement the concept.\nFinally, we'll show their pluses and minuses, and highlight some features of\npackages that use them.\n\nAbstract\n\nTalk outline:\n\n * Define what a coroutine is \n * Coroutine state not known to operating system \n * Difference between a thread or process \n * What state is required for tracking \n * Show how coroutines are used \n * gevent example \n * concurrence example \n * Review two implementations \n * Greenlets \n * Python based co-routines using generators \n * Advantages/Disadvantages \n * Differentiating features of packages that use them \n * Concurrence \n * Gevent \n * Eventlets \n\n", "quality_notes": "", "copyright_text": "Creative Commons Attribution-NonCommercial-ShareAlike 3.0", "embed": "", "thumbnail_url": "", "duration": null, "video_ogv_length": 129516368, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "", "whiteboard": "", "recorded": "2011-03-11", "added": "2012-02-23T04:20:00", "updated": "2014-04-08T20:28:27.945" }