带有后端的 GWT 项目
更新：对于“后端”一词的含糊之处，我深表歉意。该问题的定义是：
“在 Web 内容管理系统中，术语前端和后端可能分别指面向最终用户的 CMS 视图和管理视图。”
我们想要创建一个具有后端管理界面的应用程序。我见过很多使用后端的产品，但我不知道它们是如何工作或设计的。
我最大的疑问是：
- 将更改（使客户端了解更改）从管理员视图传递到客户端视图的常用方法是什么？
- 我应该将应用程序分成两部分并为每个应用程序提供不同的端口还是将所有内容放在一起？
- 第二个问题的方法会影响第一个问题吗？
其他详细信息包括：
是一个使用 GWT 和 JAVA 的 Web 项目。它将部署在 Jboss 服务器上。
关于端口：由于一切都是网络，我想知道是否应该将应用程序分成 2 部分，并让服务器监听 2 个端口（通过代理等）并相应地重定向，或者允许通过前端访问管理后端。
UPDATE: My apologies for the ambiguity of the word back end. The definiton used for this question is:
"In Web content management systems the terms front end and back end may refer to the end-user facing views of the CMS and the administrative views respectively."
We want to create an app which got a backend administration interface. I've seen plenty of products using a backend but I got no idea of how they work or are desgined.
Among my biggest doubts are:
- Whats the common approach to pass changes (make the client aware of changes) from the admin to the client view?
- Should I split the apps in 2 and give each a different port or just everything together?
- Would question number 2 approach would affect number 1?
Additional details are:
Is a web project using GWT with JAVA. It will be deployed on a Jboss server.
About the ports: Since everything is web, what I was wondering is if I should split the app in 2 and have the server listening to 2 ports (via proxy, whatever) and redirect accordingly, or allow access to administration backend through the front end.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这里有一个评估技术和设计的快速技巧，可以帮助您比较完成工作的正确方法（适合您）：编写一个猜数字游戏，计算机选择一个数字并告诉您您的猜测是否太高或太低了。该游戏非常简单，不会分散您对正在评估的技术的思考，但它要求您对 UI 和控制流在特定工具链中的工作方式有基本的了解。它还允许您提出比上述问题更具体的问题，这本质上是一项民意调查。
Here's a quick trick for evaluating technologies and designs to help you make comparisons about the Right Way (for you) to get your job done: Write a number-guessing game where the computer picks a number and tells you if your guess is too high or too low. The game is simple enough that it's not a distraction from thinking about the technology that you're evaluating, but it requires that you gain a base understanding of how UI and control flow work in the particular toolchain. It also allows you to formulate much more specific questions than the one above, which is essentially an opinion poll.
你的问题2很大程度上取决于你使用的技术。如果您使用的是j2ee及其附属技术堆栈，您可能根本不需要区分端口，因为一切都是Web。这会影响你的第一点，因为此时整个网络通信是拉式的而不是推式的——你的客户端问服务器：“有新闻吗？”
由于您的问题被标记为“网络开发”，我认为“网络”是您目前的设计选择？
这可能是 python、php、java（带有 GWT、JSF 等），
你有一个巨大的工具集可供选择，我认为你需要做出选择，因为否则你会迷失......
Your question 2 LARGELY depends on which technique you are using. If you are using the j2ee and subsidary technology stacks, you might not need to distinguish between ports at all because everything is web. This would affect your point #1 because whole webcommunications is at this time rather pull than push - your client asks the server: "Are there news?"
As your question is tagged "web-development" I assume that "web" is your design choice for now?
That could be python, php, java (with GWT, JSF, etc)
You've got a huge toolset to pick of, I think you need to make a choice, because otherwise you'll get lost...