AIOHTTP JSON RPC
JSON-RPC server and client implementation based on aiohttp.
Server example
from aiohttp import web
from aiohttp_jsonrpc import handler
class JSONRPCExample(handler.JSONRPCView):
def rpc_test(self):
return None
def rpc_args(self, *args):
return len(args)
def rpc_kwargs(self, **kwargs):
return len(kwargs)
def rpc_args_kwargs(self, *args, **kwargs):
return len(args) + len(kwargs)
def rpc_exception(self):
raise Exception("YEEEEEE!!!")
def rpc_test_notification(self):
print("Notification received")
app = web.Application()
app.router.add_route('*', '/', JSONRPCExample)
if __name__ == "__main__":
import logging
logging.basicConfig(level=logging.INFO)
web.run_app(app, print=logging.info)Client example
import asyncio
from aiohttp_jsonrpc.client import ServerProxy
loop = asyncio.get_event_loop()
client = ServerProxy("http://127.0.0.1:8080/", loop=loop)
async def main():
print(await client.test())
# Or via __getitem__
method = client['args']
notification = client.create_notification("test_notification")
print(await method(1, 2, 3))
await notification()
results = await client.batch(
client['test'],
client['test'].prepare(),
client['args'].prepare(1, 2, 3),
client['not_found'].prepare(1, 2, 3),
# notify with params
notification.prepare(),
# notification without params
notification,
)
print(results)
client.close()
if __name__ == "__main__":
loop.run_until_complete(main())1 maintainer
Metadata
1 maintainer
Release files for aiohttp-jsonrpc 0.4.0
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 |
|---|---|---|---|---|
| aiohttp-jsonrpc-0.4.0.tar.gz | 8.3 kB | Without provenance | Details for aiohttp-jsonrpc-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aiohttp_jsonrpc-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for aiohttp_jsonrpc-0.4.0-py3-none-any.whl |
Total release size: 17.3 kB
Release files / aiohttp-jsonrpc-0.4.0.tar.gz
| Download URL | aiohttp-jsonrpc-0.4.0.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bd05afe985c4d50e500dcf2f9fc00a61a24eb6036857f49372d19cd11416351
|
|
BLAKE2b-256 checksum How to use checksums |
8a65dbcc69c5d6e952c8c2bfdbfe3f9783f4e4c1816fa93916a045a52c9d5506
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.0 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.10.2
|
Release files / aiohttp_jsonrpc-0.4.0-py3-none-any.whl
| Download URL | aiohttp_jsonrpc-0.4.0-py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdd34a5f6c689653c75ba68146422990a0fce6c830d88c8fbf69de84dab2566f
|
|
BLAKE2b-256 checksum How to use checksums |
e264b9fee2d2ad6ad3c1555cbf86f34336e41532047aa48028b21fc20c0a32f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.0 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.10.2
|
Security for aiohttp-jsonrpc 0.4.0
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.
