/usr/share/doc/python-socketio-doc/html/index.html is in python-socketio-doc 0.3.6-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Gevent-socketio documentation — gevent-socketio 0.3.1 documentation</title>
<link rel="stylesheet" href="_static/classic.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: './',
VERSION: '0.3.1',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="top" title="gevent-socketio 0.3.1 documentation" href="#" />
</head>
<body role="document">
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="nav-item nav-item-0"><a href="#">gevent-socketio 0.3.1 documentation</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="gevent-socketio-documentation">
<h1>Gevent-socketio documentation<a class="headerlink" href="#gevent-socketio-documentation" title="Permalink to this headline">¶</a></h1>
<div class="toctree-wrapper compound">
<ul class="simple">
</ul>
</div>
<div class="section" id="introduction">
<h2>Introduction<a class="headerlink" href="#introduction" title="Permalink to this headline">¶</a></h2>
<p>Socket.IO is a WebSocket-like abstraction that enables real-time
communication between a browser and a server. <code class="docutils literal"><span class="pre">gevent-socketio</span></code> is a
Python implementation of the protocol.</p>
<p>The reference server implementation of Socket.IO runs on Node.js and was
developed by LearnBoost. There are now server implementations in a
variety of languages.</p>
<p>One aim of this project is to provide a single <code class="docutils literal"><span class="pre">gevent</span></code>-based
API that works across the different WSGI-based web frameworks out
there (Pyramid, Pylons, Flask, web2py, Django, etc...). Only ~3 lines
of code are required to tie-in <code class="docutils literal"><span class="pre">gevent-socketio</span></code> in your framework.
Note: you need to use the <code class="docutils literal"><span class="pre">gevent</span></code> python WSGI server to use
<code class="docutils literal"><span class="pre">gevent-socketio</span></code>.</p>
<p><strong>Namespaces</strong>: since you mostly have <strong>one</strong> websocket/socket.io
endpoint per website, it is important to be able to namespace the
different real-time activities of the different pages or parts of
your site, just like you need routes to map URLs to different parts
of your code. The Socket.IO 0.7+ namespaces are a welcome addition,
and if you don’t use Socket.IO, you’ll probably end-up writing your
own namespacing mechanism at some point.</p>
<p><strong>Named events</strong>: To distinguish the messages that are coming and
going, you most probably want to give them some name. Here again, not
using Socket.IO, you will find yourself implementing a way to tag your
packets with names representing different tasks or actions to
perform. With Socket.IO 0.6 or with normal WebSockets, you would
probably encode a JSON object with one of the keys that is reserved
for that (I used <code class="docutils literal"><span class="pre">{"type":</span> <span class="pre">"submit_something"}</span></code>. Socket.IO 0.7+
implements named events, which put that information in a terse form on
the wire. It also allows you to define callbacks, that can be
acknowledged by the other endpoint, and then fire back your function
with some return parameters. Something great for RPC, that you’d need
to implement yourself the moment you need it.</p>
<p><strong>Transports</strong>: One of the main feature of Socket.IO is the
abstraction of the transport, that gives you real-time web support
down to Internet Explorer 6.0, using long-polling methods. It will
also use native WebSockets when available to the browser, for even
lower latencies. Currently supported transports: <code class="docutils literal"><span class="pre">websocket</span></code>,
<code class="docutils literal"><span class="pre">flashsocket</span></code>, <code class="docutils literal"><span class="pre">htmlfile</span></code>, <code class="docutils literal"><span class="pre">xhr-multipart</span></code>, <code class="docutils literal"><span class="pre">xhr-polling</span></code>,
<code class="docutils literal"><span class="pre">jsonp-polling</span></code>.</p>
<p>This implementation covers nearly all the features of the Socket.IO
0.7+ (up to at least 0.9.1) protocol, with events, callbacks. It adds
security in a pythonic way with granular ACLs (which don’t exist in
the Node.js version) at the method level. The project has several
examples in the source code and in the documentation. Any addition
and fixes to the docs are warmly welcomed.</p>
</div>
<div class="section" id="concepts">
<h2>Concepts<a class="headerlink" href="#concepts" title="Permalink to this headline">¶</a></h2>
<p>In order to understand the following documentation articles, let’s
clarify some of the terms used:</p>
<p>A <strong>Namespace</strong> is like a controller in the MVC world. It encompasses
a set of methods that are logically in it. For example, the
<code class="docutils literal"><span class="pre">send_private_message</span></code> event would be in the <code class="docutils literal"><span class="pre">/chat</span></code> namespace, as
well as the <code class="docutils literal"><span class="pre">kick_ban</span></code> event. Whereas the <code class="docutils literal"><span class="pre">scan_files</span></code> event
would be in the <code class="docutils literal"><span class="pre">/filesystem</span></code> namespace. Each namespace is
represented by a sub-class of <code class="xref py py-class docutils literal"><span class="pre">BaseNamespace</span></code>. A simple
example would be, on the client side (the browser):</p>
<div class="highlight-javascript"><div class="highlight"><pre><span class="kd">var</span> <span class="nx">socket</span> <span class="o">=</span> <span class="nx">io</span><span class="p">.</span><span class="nx">connect</span><span class="p">(</span><span class="s2">"/chat"</span><span class="p">);</span>
</pre></div>
</div>
<p>having loaded the <code class="docutils literal"><span class="pre">socket.io.js</span></code> library somewhere in your <head>.
On the server (this is a Pyramid example, but its pretty much the same
for other frameworks):</p>
<div class="highlight-python"><div class="highlight"><pre><span class="kn">from</span> <span class="nn">socketio.namespace</span> <span class="kn">import</span> <span class="n">BaseNamespace</span>
<span class="k">class</span> <span class="nc">ChatNamespace</span><span class="p">(</span><span class="n">BaseNamespace</span><span class="p">):</span>
<span class="k">def</span> <span class="nf">on_chat</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">msg</span><span class="p">):</span>
<span class="bp">self</span><span class="o">.</span><span class="n">emit</span><span class="p">(</span><span class="s1">'chat'</span><span class="p">,</span> <span class="n">msg</span><span class="p">)</span>
<span class="k">def</span> <span class="nf">socketio_service</span><span class="p">(</span><span class="n">request</span><span class="p">):</span>
<span class="n">socketio_manage</span><span class="p">(</span><span class="n">request</span><span class="o">.</span><span class="n">environ</span><span class="p">,</span> <span class="p">{</span><span class="s1">'/chat'</span><span class="p">:</span> <span class="n">ChatNamespace</span><span class="p">},</span>
<span class="n">request</span><span class="p">)</span>
<span class="k">return</span> <span class="s2">"out"</span>
</pre></div>
</div>
<p>Here we use <a class="reference internal" href="main.html#socketio.socketio_manage" title="socketio.socketio_manage"><code class="xref py py-func docutils literal"><span class="pre">socketio.socketio_manage()</span></code></a> to start the Socket.IO
machine, and handle the real-time communication.</p>
<p>You will come across the notion of a <code class="docutils literal"><span class="pre">Socket</span></code>. This is a virtual
socket, that abstracts the fact that some transports are long-polling
and others are stateful (like a Websocket), and exposes the same
functionality for all. You can have many namespaces inside a Socket,
each delimited by their name like <code class="docutils literal"><span class="pre">/chat</span></code>, <code class="docutils literal"><span class="pre">/filesystem</span></code> or
<code class="docutils literal"><span class="pre">/foobar</span></code>. Note also that there is a global namespace, identified
by an empty string. Some times, the global namespace has special
features, for backwards compatibilty reasons (we only have a global
namespace in version 0.6 of the protocol). For example, disconnecting
the global namespace means disconnect the full socket. Disconnecting
a qualified namespace, on the other hand, only removes access to that
namespace.</p>
<p>The <code class="docutils literal"><span class="pre">Socket</span></code> is responsible from taking the <cite>packets</cite>, which are, in
the realm of a <code class="docutils literal"><span class="pre">Namespace</span></code> or a <code class="docutils literal"><span class="pre">Socket</span></code> object, a dictionary that
looks like:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="p">{</span><span class="s2">"type"</span><span class="p">:</span> <span class="s2">"event"</span><span class="p">,</span>
<span class="s2">"name"</span><span class="p">:</span> <span class="s2">"launch_superhero"</span><span class="p">,</span>
<span class="s2">"args"</span><span class="p">:</span> <span class="p">[</span><span class="s2">"Superman"</span><span class="p">,</span> <span class="mi">123</span><span class="p">,</span> <span class="s2">"km"</span><span class="p">,</span> <span class="p">{</span><span class="s2">"hair_color"</span><span class="p">:</span> <span class="s2">"brown"</span><span class="p">}]}</span>
</pre></div>
</div>
<p>These packets are serialized in a compact form when its time to put
them on the wire. Socket.IO also has some optimizations if we need to
send many packets on some long-polling transports.</p>
<p>At this point, if you don’t know <code class="docutils literal"><span class="pre">gevent</span></code>, you probably will want to
learn a bit more about it, since it is the base you will be working
on:</p>
<blockquote>
<div><a class="reference external" href="http://www.gevent.org/">http://www.gevent.org/</a></div></blockquote>
</div>
<div class="section" id="getting-started">
<h2>Getting started<a class="headerlink" href="#getting-started" title="Permalink to this headline">¶</a></h2>
<p>Until we have a fully-fledged tutorial, please check out our example
applications and the API documentation.</p>
<p>You can see a video that shows <code class="docutils literal"><span class="pre">gevent-socketio</span></code> in a live coding
presentation here:</p>
<blockquote>
<div><a class="reference external" href="http://pyvideo.org/video/1573/gevent-socketio-cross-framework-real-time-web-li">http://pyvideo.org/video/1573/gevent-socketio-cross-framework-real-time-web-li</a></div></blockquote>
<p>To learn how to build your Namespace (the object dealing with requests and replies), see:</p>
<blockquote>
<div><a class="reference internal" href="namespace.html#namespace-module"><span>socketio.namespace</span></a></div></blockquote>
<p>See this doc for different servers integration:</p>
<blockquote>
<div><a class="reference internal" href="server_integration.html#server-integration"><span>Server integration layers</span></a></div></blockquote>
</div>
<div class="section" id="examples">
<h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">¶</a></h2>
<p>The <code class="docutils literal"><span class="pre">gevent-socketio</span></code> repository holds several examples:</p>
<blockquote>
<div><p><a class="reference external" href="https://github.com/abourget/gevent-socketio/tree/master/examples">https://github.com/abourget/gevent-socketio/tree/master/examples</a></p>
<ul class="simple">
<li><code class="docutils literal"><span class="pre">simple_chat</span></code> is a bare-bone WSGI app with a minimal socketio integration</li>
<li><code class="docutils literal"><span class="pre">simple_pyramid_chat</span></code> is a simple chat application built on Pyramid</li>
<li><code class="docutils literal"><span class="pre">live_cpu_graph</span></code> is a simple realtime CPU graph (linux only)</li>
<li><code class="docutils literal"><span class="pre">twitter_stream</span></code> is a streaming feed of twitter updates</li>
<li><code class="docutils literal"><span class="pre">pyramid_backbone_redis_chat</span></code> is a Pyramid app using backbone.js and redis for pubsub</li>
<li><code class="docutils literal"><span class="pre">pyramid_backbone_redis_chat_persistence</span></code> is a Pyramid app using backbone.js, redis for pubsub and features persistence</li>
<li><code class="docutils literal"><span class="pre">testapp</span></code> is the app we use to test the different features, so there are a couple of more advanced use-cases demonstrated there</li>
</ul>
</div></blockquote>
<p><code class="docutils literal"><span class="pre">pyvore</span></code> is an application that was developed to serve as real-time
chat in conferences like the PyCon:</p>
<blockquote>
<div><a class="reference external" href="https://github.com/sontek/pyvore">https://github.com/sontek/pyvore</a></div></blockquote>
<p>This app is a Django tic-tac-toe application that uses the latest
<code class="docutils literal"><span class="pre">gevent-socketio</span></code>:</p>
<blockquote>
<div><a class="reference external" href="https://github.com/sontek/django-tictactoe">https://github.com/sontek/django-tictactoe</a></div></blockquote>
</div>
<div class="section" id="security">
<h2>Security<a class="headerlink" href="#security" title="Permalink to this headline">¶</a></h2>
<p><code class="docutils literal"><span class="pre">gevent-socketio</span></code> provides method-level security, using an ACL
model. You can read more about it in the <a class="reference internal" href="namespace.html#namespace-module"><span>socketio.namespace</span></a>, but
a basic example to secure one namespace would look like:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="k">class</span> <span class="nc">AdminInterface</span><span class="p">(</span><span class="n">BaseNamespace</span><span class="p">):</span>
<span class="k">def</span> <span class="nf">get_initial_acl</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
<span class="sd">"""Everything is locked at first"""</span>
<span class="k">return</span> <span class="p">[]</span>
<span class="k">def</span> <span class="nf">initialize</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
<span class="c1"># This here assumes you have passed in a `request`</span>
<span class="c1"># to your socketio_manage() call, it has that</span>
<span class="c1"># `is_admin` attribute</span>
<span class="k">if</span> <span class="ow">not</span> <span class="n">request</span><span class="o">.</span><span class="n">is_admin</span><span class="p">:</span>
<span class="k">return</span>
<span class="k">else</span><span class="p">:</span>
<span class="bp">self</span><span class="o">.</span><span class="n">lift_acl_restrictions</span><span class="p">()</span>
<span class="k">def</span> <span class="nf">on_blahblahblah</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">data</span><span class="p">):</span>
<span class="sd">"""This can't be access until `lift_acl_restrictions()` has</span>
<span class="sd"> been called</span>
<span class="sd"> """</span>
<span class="k">pass</span>
</pre></div>
</div>
</div>
<div class="section" id="api-docs">
<h2>API docs<a class="headerlink" href="#api-docs" title="Permalink to this headline">¶</a></h2>
<p>API documentation is where most of the juice/meat is. Read through
and you’ll (hopefully) understand everything you need about
<code class="docutils literal"><span class="pre">gevent-socketio</span></code>.</p>
<p>The manager is the function you call from your framework. It is in:</p>
<blockquote>
<div><a class="reference internal" href="main.html#module-socketio" title="socketio"><code class="xref py py-mod docutils literal"><span class="pre">socketio</span></code></a></div></blockquote>
<p><strong>Namespaces</strong> are the main interface the developer is going to use.
You mostly define your own BaseNamespace derivatives, and
gevent-socketio maps the incoming messages to your methods
automatically:</p>
<blockquote>
<div><a class="reference internal" href="namespace.html#module-socketio.namespace" title="socketio.namespace"><code class="xref py py-mod docutils literal"><span class="pre">socketio.namespace</span></code></a></div></blockquote>
<p><strong>Mixins</strong> are components you can add to your namespaces, to provided
added functionality.</p>
<blockquote>
<div><a class="reference internal" href="mixins.html#module-socketio.mixins" title="socketio.mixins"><code class="xref py py-mod docutils literal"><span class="pre">socketio.mixins</span></code></a></div></blockquote>
<p><strong>Sockets</strong> are the virtual tunnels that are established and
abstracted by the different Transports. They basically expose
socket-like send/receive functionality to the Namespace objects. Even
when we use long-polling transports, only one Socket is created per
browser.</p>
<blockquote>
<div><a class="reference internal" href="virtsocket.html#module-socketio.virtsocket" title="socketio.virtsocket"><code class="xref py py-mod docutils literal"><span class="pre">socketio.virtsocket</span></code></a></div></blockquote>
<p><strong>Packet</strong> is a library that handle the decoding of the messages
encoded in the Socket.IO dialect. They take dictionaries for
encoding, and return decoded dictionaries also.</p>
<blockquote>
<div><a class="reference internal" href="packet.html#module-socketio.packet" title="socketio.packet"><code class="xref py py-mod docutils literal"><span class="pre">socketio.packet</span></code></a></div></blockquote>
<p><strong>Handler</strong> is a lower-level transports handler. It is responsible
for calling your WSGI application</p>
<blockquote>
<div><a class="reference internal" href="handler.html#module-socketio.handler" title="socketio.handler"><code class="xref py py-mod docutils literal"><span class="pre">socketio.handler</span></code></a></div></blockquote>
<p><strong>Transports</strong> are responsible for translating the different fallback
mechanisms to one abstracted Socket, dealing with payload encoding,
multi-message multiplexing and their reverse operation.</p>
<blockquote>
<div><a class="reference internal" href="transports.html#module-socketio.transports" title="socketio.transports"><code class="xref py py-mod docutils literal"><span class="pre">socketio.transports</span></code></a></div></blockquote>
<p><strong>Server</strong> is the component used to hook Gevent and its WSGI server to
the WSGI app to be served, while dispatching any Socket.IO related
activities to the <cite>handler</cite> and the <cite>transports</cite>.</p>
<blockquote>
<div><a class="reference internal" href="server.html#module-socketio.server" title="socketio.server"><code class="xref py py-mod docutils literal"><span class="pre">socketio.server</span></code></a></div></blockquote>
<p>Auto-generated indexes:</p>
<ul class="simple">
<li><a class="reference internal" href="genindex.html"><span>Index</span></a></li>
<li><a class="reference internal" href="py-modindex.html"><span>Module Index</span></a></li>
</ul>
</div>
<div class="section" id="references">
<h2>References<a class="headerlink" href="#references" title="Permalink to this headline">¶</a></h2>
<p>LearnBoost’s node.js version is the reference implementation, you can
find the server component at this address:</p>
<blockquote>
<div><a class="reference external" href="https://github.com/learnboost/socket.io">https://github.com/learnboost/socket.io</a></div></blockquote>
<p>The client JavaScript library’s development branch is here:</p>
<blockquote>
<div><a class="reference external" href="https://github.com/LearnBoost/socket.io-client">https://github.com/LearnBoost/socket.io-client</a></div></blockquote>
<p>The specifications to the protocol are somehow in this repository:</p>
<blockquote>
<div><a class="reference external" href="https://github.com/LearnBoost/socket.io-spec">https://github.com/LearnBoost/socket.io-spec</a></div></blockquote>
<p>This is the original wow-website:</p>
<blockquote>
<div><a class="reference external" href="http://socket.io">http://socket.io</a></div></blockquote>
<p>Here is a list of the different frameworks integration to date,
although not all have upgraded to the latest version of
gevent-socketio:</p>
<blockquote>
<div><ul class="simple">
<li>pyramid_socketio: <a class="reference external" href="https://github.com/abourget/pyramid_socketio">https://github.com/abourget/pyramid_socketio</a></li>
<li>django-socketio: <a class="reference external" href="https://github.com/stephenmcd/django-socketio">https://github.com/stephenmcd/django-socketio</a></li>
</ul>
</div></blockquote>
<p>The Flask guys will be working on an integration layer soon.</p>
</div>
<div class="section" id="contacts">
<h2>Contacts<a class="headerlink" href="#contacts" title="Permalink to this headline">¶</a></h2>
<p>For any questions, you can use the Issue tracking at Github:</p>
<blockquote>
<div><a class="reference external" href="https://github.com/abourget/gevent-socketio">https://github.com/abourget/gevent-socketio</a>
<a class="reference external" href="https://github.com/abourget/gevent-socketio/issues">https://github.com/abourget/gevent-socketio/issues</a></div></blockquote>
<p>The mailing list:</p>
<blockquote>
<div><a class="reference external" href="https://groups.google.com/forum/#!forum/gevent-socketio">https://groups.google.com/forum/#!forum/gevent-socketio</a></div></blockquote>
<p>The maintainers:</p>
<blockquote>
<div><a class="reference external" href="https://twitter.com/bourgetalexndre">https://twitter.com/bourgetalexndre</a>
<a class="reference external" href="https://twitter.com/sontek">https://twitter.com/sontek</a></div></blockquote>
</div>
<div class="section" id="credits">
<h2>Credits<a class="headerlink" href="#credits" title="Permalink to this headline">¶</a></h2>
<p><strong>Jeffrey Gellens</strong> for starting and polishing this project over the years.</p>
<p>PyCon 2012 and the Sprints, for bringing this project up to version
0.9 of the protocol.</p>
<p>Current maintainers:</p>
<blockquote>
<div><ul class="simple">
<li>Alexandre Bourget</li>
<li>John Anderson</li>
</ul>
</div></blockquote>
<p>Contributors:</p>
<blockquote>
<div><ul class="simple">
<li>Denis Bilenko</li>
<li>Bobby Powers</li>
<li>Lon Ingram</li>
<li>Eugene Baumstein</li>
<li>Sébastien Béal</li>
<li>jpellerin (JP)</li>
<li>Philip Neustrom</li>
<li>Jonas Obrist</li>
<li>fabiodive</li>
<li>Dan O’Neill</li>
<li>Whit Morriss</li>
<li>Chakib (spike) Benziane</li>
<li>Vivek Venugopalan</li>
<li>Vladimir Protasov</li>
<li>Bruno Bigras</li>
<li>Gabriel de Labacheliere</li>
<li>Flavio Curella</li>
<li>thapar</li>
<li>Marconi Moreto</li>
<li>sv1jsb</li>
<li>Cliff Xuan</li>
<li>Matt Billenstein</li>
<li>Rolo</li>
<li>Anthony Oliver</li>
<li>Pierre Giraud</li>
<li>m0sth8</li>
<li>Daniel Swarbrick</li>
</ul>
</div></blockquote>
</div>
<div class="section" id="todo">
<h2>TODO<a class="headerlink" href="#todo" title="Permalink to this headline">¶</a></h2>
<p>How to integrate your framework’s “session” object (Beaker, memcached, or file-based). Beware: this can be tricky. You need to manage that yourself.</p>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<h3><a href="#">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Gevent-socketio documentation</a><ul>
<li><a class="reference internal" href="#introduction">Introduction</a></li>
<li><a class="reference internal" href="#concepts">Concepts</a></li>
<li><a class="reference internal" href="#getting-started">Getting started</a></li>
<li><a class="reference internal" href="#examples">Examples</a></li>
<li><a class="reference internal" href="#security">Security</a></li>
<li><a class="reference internal" href="#api-docs">API docs</a></li>
<li><a class="reference internal" href="#references">References</a></li>
<li><a class="reference internal" href="#contacts">Contacts</a></li>
<li><a class="reference internal" href="#credits">Credits</a></li>
<li><a class="reference internal" href="#todo">TODO</a></li>
</ul>
</li>
</ul>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/index.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="nav-item nav-item-0"><a href="#">gevent-socketio 0.3.1 documentation</a> »</li>
</ul>
</div>
<div class="footer" role="contentinfo">
© Copyright 2011-2016, Jeffrey Gelens, Alexandre Bourget, and John Anderson.
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.3.6.
</div>
</body>
</html>
|