Does Reflex support standard front-end and back-end separation?

[jinhong-china]

I don't understand front-end knowledge like Vue/React, but I am very good at Python back-end I want to write front-end UI using Python and compile it into standard front-end code, which can be hosted directly on nginx without the need for websocket. The front-end and back-end only use standard API communication May I ask if Reflex can meet these requirements? If possible, what should I pay attention to?

[masenf]

it is technically possible. you can pass app = rx.App(enable_state=False) to disable the websocket and make a stateless app. The challenge will arise when attempting to use standard API communication, because the open source package doesn't expose the javascript fetch wrapper for making the calls. You can use a combination of rx.call_script (with javascript code) and rx._x.client_state to store values for the session. This is something that we want to support more completely in the future, but for the moment it's very experimental.

[jinhong-china]

Thank you for your reply. I am glad to hear that Reflex is working hard to achieve standard front-end and back-end separation. For backend engineers who are not familiar with Vue/React, this is exciting news as they can independently write frontend pages, as most of the time front-end and back-end separation is required. I think WebSocket should be an advanced development option in real-time interaction scenarios
Is the standard front-end and back-end separation achieved solely by using enable_state=False? What should be noted in code organization? I know Reflex has a class for managing states. If I want to get a standard front-end and back-end separation project (using my existing FastAPI as the API node for back-end business), what are the differences in the internal writing of classes? And if there are any other things to pay attention to, I am willing to use one of my personal projects for experimentation

[jinhong-china]

理论上是可行的。您可以传递参数app = rx.App(enable_state=False)来禁用 WebSocket，从而创建一个无状态应用程序。但当尝试使用标准 API 通信时，就会遇到挑战，因为开源软件包没有公开fetch用于发起调用的 JavaScript 封装层。您可以结合使用rx.call_script（带有 JavaScript 代码的）和rx._x.client_state来存储会话值。我们希望在未来更全面地支持此功能，但目前它仍处于实验阶段。

I just conducted a test and found that when enable_state=true, clicking the button can interact with the backend fastAPI normally. After setting enable_ste=false, clicking the button did not respond. Even the most basic printing in the login function will not print. If i want to develop applications with stateless mode, whether or not i have to write JavaScript separately for click actions without using Reflex components attribute?
Does Reflex currently not support stateless mode, or does it require a different development paradigm from the official tutorial? Can the official provide a development tutorial for stateless mode?

[masenf]

Reflex is, by nature, a monolithic framework where the frontend and backend code are tightly coupled. This is what allows for fast iteration speed and development.

We don't currently provide documentation for stateless mode, because it is so limited.

In the future, i'd like to see a ClientState and converting some Var Operation-only methods to be considered "frontend event handlers", but these things are not currently the team's focus.