Asphalt application framework (core)
.. image:: https://travis-ci.org/asphalt-framework/asphalt.svg?branch=master :target: https://travis-ci.org/asphalt-framework/asphalt :alt: Build Status .. image:: https://coveralls.io/repos/github/asphalt-framework/asphalt/badge.svg?branch=master :target: https://coveralls.io/github/asphalt-framework/asphalt?branch=master :alt: Code Coverage .. image:: https://readthedocs.org/projects/asphalt/badge/?version=latest :target: https://asphalt.readthedocs.io/en/latest/?badge=latest :alt: Documentation Status
Asphalt is an asyncio_ based microframework for network oriented applications.
Its highlight features are:
Type hints_ and
semantic versioning_ used throughout the core and all component libraries
Asphalt can be used to make any imaginable kind of networked application, ranging from trivial command line tools to highly complex component hierarchies that start multiple network servers and/or clients using different protocols.
What really sets Asphalt apart from other frameworks is its resource sharing system – the kind of functionality usually only found in bulky application server software. Asphalt components publish their services as resources in a shared context. Components can build on resources provided by each other, making it possible to create components that offer highly sophisticated functionality with relatively little effort.
.. _asyncio: https://docs.python.org/3/library/asyncio.html .. _uvloop: https://github.com/MagicStack/uvloop .. _tokio: https://github.com/PyO3/tokio .. _Type hints: https://www.python.org/dev/peps/pep-0484/ .. _semantic versioning: http://semver.org/