Open Archmonger opened 1 year ago
@rmorshea I can also develop a WSGI variant of this. However, it will only work with WSGI webservers that have official websocket support: werkzeug
, gunicorn
, eventlet
, and gevent
.
The design of this would be largely based on flask-sock
.
If we could take a similar approach to simplifying the flask/tornado backends that would be good too. If not, doesn't seem necessary. Regardless, probably should be done in a separate PR.
WSGI middleware would grant us compatibility with the following frameworks: https://wsgi.readthedocs.io/en/latest/frameworks.html
Unfortunately tornado uses its own custom API, so we would either need to drop support for tornado or keep using configure()
for it. To be honest, I'm leaning towards dropping support because tornado does not have built-in integration with Jinja template tags.
I'm realizing that tornado support should almost certainly be spun off into its own package, similar to ReactPy-Django.
Current Situation
Currently we perform ASGI routing via backend-specific APIs. However, it is much easier to gain broad compatibility via ASGI middleware. Additionally, we should have a "standalone" mode where ReactPy can run in a production configuration without any backend.
I originally pitched this concept a long time ago during our development of our
configure()
function.Proposed Actions
Create a ReactPy ASGI application that can also function as middleware.
Interface Design
Implementation Draft