django/daphne
1
1
Fork 0
mirror of https://github.com/django/daphne.git synced 2025-07-30 16:59:46 +03:00
Code Issues Packages Projects Releases Wiki Activity

Few more spec clarifications

Browse Source
This commit is contained in:
Andrew Godwin 2017-03-19 12:26:20 -07:00
parent 528cd89f4e
commit 1f2538f5b8
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/asgi.rst
View File

@ -36,16 +36,16 @@ an abstraction that allows for data to be sent and received at any time,
and from different application threads or processes. and from different application threads or processes.
It also take the principle of turning protocols into Python-compatible, It also take the principle of turning protocols into Python-compatible,
asynchronous-friendly sets of messages and generalises it into two sections; asynchronous-friendly sets of messages and generalises it into two parts;
a standardised interface for communication and to build servers around (this a standardised interface for communication and to build servers around (this
document), and a set of standard message formats for each protocol (the document), and a set of standard :ref:`message formats for each protocol <asgi_sub_specifications>`.
sub-specifications, linked above).
Its primary design is for HTTP, however, and part of this design is Its primary goal is to provide a way to write HTTP/2 and WebSocket code,
ensuring there is an easy path to use both alongside normal HTTP handling code, however, and part of this design is
existing WSGI servers and applications, as a large majority of Python ensuring there is an easy path to use both existing WSGI servers and
web usage relies on WSGI and providing an easy path forwards is critical applications, as a large majority of Python web usage relies on WSGI and
to adoption. providing an easy path forwards is critical to adoption. Details on that
interoperability are covered in :doc:`/asgi/www`.
The end result of this process has been a specification for generalised The end result of this process has been a specification for generalised
inter-process communication between Python processes, with a certain set of inter-process communication between Python processes, with a certain set of
@ -55,6 +55,7 @@ task queues, but it is intended that it could be used for things like
distributed systems communication, or as the backbone of a service-oriented distributed systems communication, or as the backbone of a service-oriented
architecure for inter-service communication. architecure for inter-service communication.
Overview Overview
======== ========
@ -104,7 +105,8 @@ contain only the following types to ensure serializability:
* Byte strings * Byte strings
* Unicode strings * Unicode strings
* Integers (no longs) * Integers (within the signed 64 bit range)
* Floating point numbers (within the IEEE 754 double precision range)
* Lists (tuples should be treated as lists) * Lists (tuples should be treated as lists)
* Dicts (keys must be unicode strings) * Dicts (keys must be unicode strings)
* Booleans * Booleans