The problem with ProtocolBuffer as it stands now is that the official Python library for ProtocolBuffer is not very pythonic, There’s already an experimental gRPC implementation based on grpcio, but without true support for asynchronous calls because that is not supported by the official Python library. Streaming gRPC (HTTP/2) implementation with e.g. This would be the only solution that fully supports streaming and can be used in the browser today. Streaming WebSocket implementation with aiohttp OpenAPI (Swagger) schema service for API reflectionĪn unordered list of potential future features:ĬLI for generating sharable stubs from services Message generation from request arguments To install Venom using ‘pip’ for use with flask, run: pip install flask-venom Road mapĪ list of major features required for the first release: To install Venom using ‘pip’ for use with aiohttp, run: pip install venom The final version will likely require Python 3.6. Unary gRPC protocol implementation using grpcioĭocumentation currently is minimal! Head to the examples/ folder for more details. Unary HTTP/1 protocol implementation using aiohttp (asynchronous) or flask (synchronous only) The currently available implementations are: The framework is designed to support different server implementations. So far, Venom RPC supports unary requests & replies that are defined as methods on services. The aim of Venom is to provide a low overhead framework for RPC service development specifically in Python while sticking to language agnostic communication standards. The framework uses a simple message format for communications, compatible with the ProtocolBuffer format. It will support unary (single message) and streaming communication patterns inspired by gRPC. It features a simple, testable, composable service model and support for the Python 3 typing module. Venom is an upcoming RPC framework for Python.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |