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
|
Structure of tinyrpc
====================
``tinyrpc`` architectually considers three layers: Transport, Protocol and
Dispatch.
The Transport-layer is responsible for receiving and sending messages. No
assumptions are made about messages, except that they are of a fixed size.
Messages are received and possibly passed on a Python strings.
In an RPC context, messages coming in (containing requests) are simply called
messages, a message sent in reply is called a reply. Replies are always
serialized responses.
On the Protocol-layer messages are decoded into a format that is protocol
independent, i.e. incoming messages are turned into requests or vice verse, while outgoing
messages can be turned from responses into replies or the other way around.
The Dispatch-layer performs the actual method calling and serializes the return
value. These can be routed back through the Protocol- and Transport-layer to
return the answer to the calling client.
Each layer is useful "on its own" and can be used seperately. If you simply
need to decode a jsonrpc_ message, without passing it on or sending it through
a transport, any :py:class:`~tinyrpc.RPCProtocol`-class is completely usable
on its own.
.. _jsonrpc: http://jsonrpc.org
|
