Spring Web 流程
我确实有一个问题，不知道用什么来替代网络流。我读到并非所有功能都应该由网络流处理。仅那些需要复杂的 xstate 管理的情况。对于那些简单的事情，例如登录、编辑或删除记录，我将使用什么作为网络流程的替代方案？
I am really having a problem about what to use as an alternative for web flow. I have read that not all functionalities should be handled by web flow. Only those which needs complex xstate management. For those easy stuffs like just login, editing or deleting records what will I use as an alternative for web flow?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Spring Web flow 是专门为实现复杂的页面流而设计的。它是Spring MVC的扩展，是指定页面导航规则和管理导航的工具。
Spring Web flow为Web应用开发中的以下主要问题提供了根本答案：
如何指定页面导航规则？
如何管理导航和对话状态？
如何保证模块化和代码复用？
它还与 JSF 组件模型集成，主要用于企业应用程序开发。没有那么多替代方案，但对于 Vaadin 组件模型，您可以将 Lexaden Web Flow 视为可能的替代方案。
Spring Web flow is specifically designed to implement complex page flows. It is an extension of Spring MVC and a tool to specify page navigation rules and manage navigation.
Spring Web flow provides fundamental answers to the following major problems in web application development:
How to specify page navigation rules?
How to manage navigation and conversational state?
How to ensure modularity and code reuse?
It is also integrated with JSF component model and used mostly for enterprise application development. There are not so many alternatives but but for Vaadin component model you can consider Lexaden Web Flow as possible alternative.
在 Web Flow 出现之前，您是如何构建网站的？
我的理解是，如果某些东西需要存储状态信息的“返回”功能（例如“向导”），那么 Web Flow 就是最佳选择。如果您没有状态，我希望您会像往常一样构建这些页面。
How did you build websites before Web Flow?
My understanding is that if something needs "back" functionality that has state information stored - like a "wizard", for example - Web Flow is the way to go. If you don't have state, I'd expect you'd build those pages as you always have.