This RPC framework uses tornado
so its very quick and asynchronous.
This framework supports regular and
asynchronous methods to be registered
with the TornRPCServer. The below example
shows both. The only difference in the
framework is how you register it.
Normal functions are registered using
"server.register()". Async functions
are registered using "server.register_async()".
For more detailed info see the docstring
for TornRPCClient and TornRPCServer.
Example:
### example server code ###
from tornado import gen
from tornrpc.server import TornRPCServer
def test(arg):
return "You said %s" % arg
@gen.coroutine
def testasync(arg):
raise gen.Return("You said async %s" % arg)
server = TornRPCServer()
server.register(test)
server.register_async(testasync)
server.start(8080)
### example client code ###
from tornrpc.client import TornRPCClient
client = TornRPCClient('localhost:8080')
client.test('hi')
client.testasync('hi')
Metadata
Release files for TornRPC 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| TornRPC-1.0.4.tar.gz | 3.7 kB | Without provenance | Details for TornRPC-1.0.4.tar.gz |
Release files / TornRPC-1.0.4.tar.gz
| Download URL | TornRPC-1.0.4.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c88253687300e685b1e85b7b1802ae7150ab2b9e60afef40370ae41a288d6d3
|
|
BLAKE2b-256 checksum How to use checksums |
faada2a161429801d20849b1d4d370271075ea1a297e1e2df7d50ae08e63c9a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TornRPC 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.