Deep Proto
This is the generated code for the common APIs for DEEP. This is generated from the project intergra/deep-proto.
Usage
The usage of these packages differs between server and clients. Please see GRPC docs for more guidance.
Client
To use this as a client:
import grpc
from deepproto.proto.tracepoint.v1.tracepoint_pb2 import Snapshot
def pollServer()
# setup the connection channel
channel = grpc.secure_channel("deep:43315", grpc.ssl_channel_credentials())
# create stub service
stub = PollConfigStub(channel)
# create request
request = PollRequest()
# send request and await response
response = stub.poll(request)
def sendSnapshot()
# setup the connection channel
channel = grpc.secure_channel("deep:43315", grpc.ssl_channel_credentials())
# create stub service
stub = SnapshotServiceStub(channel)
# create grpc snapshot message
snapshot = Snapshot()
# send snapshot, and await response
response = stub.send(snapshot)
Server
To use this as a server:
import deepproto
import grpc
from deepproto.proto.poll.v1.poll_pb2 import PollResponse, ResponseType
from deepproto.proto.poll.v1.poll_pb2_grpc import PollConfigServicer
from deepproto.proto.tracepoint.v1.tracepoint_pb2 import TracePointConfig, SnapshotResponse
from deepproto.proto.tracepoint.v1.tracepoint_pb2_grpc import SnapshotServiceServicer
def serve():
# configure GRPC
server = grpc.server(futures.ThreadPoolExecutor(max_workers=10))
# register the services
deepproto.proto.poll.v1.poll_pb2_grpc.add_PollConfigServicer_to_server(PollServicer(), server)
deepproto.proto.tracepoint.v1.tracepoint_pb2_grpc.add_SnapshotServiceServicer_to_server(SnapshotServicer(), server)
# start the server
server.add_insecure_port('[::]:43315')
server.start()
server.wait_for_termination()
class SnapshotServicer(SnapshotServiceServicer):
def send(self, request, context):
# Code to process a new snapshot
return SnapshotResponse()
class PollServicer(PollConfigServicer):
def poll(self, request, context):
# code to process a poll request
return PollResponse()
Documentation
The documentation for this project is available here.
Licensing
This project is licensed as AGPL-3.0-only.
1 maintainer
Metadata
1 maintainer
Release files for deep-proto 1.0.5
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 | |
|---|---|---|---|---|
| deep_proto-1.0.5.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deep_proto-1.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.6 kB
Release files / deep_proto-1.0.5.tar.gz
| Download URL | deep_proto-1.0.5.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
824dfe74832f9b42977ad3fa3ed4ba6bc5a44458b5c8518d3a898d20f249f24d
|
|
BLAKE2b-256 checksum How to use checksums |
1344803ec6f1d39c4a04aea75b7695ac712e25d91a391b74859b46755694df4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / deep_proto-1.0.5-py3-none-any.whl
| Download URL | deep_proto-1.0.5-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c667756df48b36d009368f3431af32db3a47dd2ced34185213c75ee0eee99e23
|
|
BLAKE2b-256 checksum How to use checksums |
ea697674133a4723306a442a12d03da6d2d78246f48480fbe2740266c62f4375
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for deep-proto 1.0.5
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.
