什么时候应该构建 Web 应用程序与胖客户端? [英] When should you build a web application vs. a thick client?

问题描述

我想听听其他人关于何时应该构建 Web 应用程序和构建胖客户端的建议.

I would like to hear other people's advice on when one should build a web application versus building a thick client.

在过去的几年里，我参与了几次关于是否应该使用 Web 浏览器界面构建应用程序(或升级旧应用程序)的讨论.通常这些是组织内部使用的内部系统，而不是大众市场的收缩包装产品，它们实际上不在公共互联网上.不过，我不想将讨论仅限于这些类型的应用程序.

Over the last few years, I have participated in several discussions about whether an application should be built (or an old application upgraded) with a web browser interface. Usually these were internal systems used within an organization, not mass-market shrink-wrap products, and they were not actually on the public Internet. I do not want to limit the discussion to these types of applications solely though.

在某些明显的情况下，应用程序应该是其中之一(例如，没有基于网络的视频编辑软件).另一方面，Javascript 库正在使浏览器中的更丰富体验变得更容易实现.

There are obvious cases where an application should be one or the other (e.g. no web based video editing software). On the other hand, Javascript libraries are making more rich experiences in the browser less difficult to implement everyday.

Javascript 库和先进的服务器端技术是否可以在客户端轻松实现诸如右键单击上下文菜单、拖放等操作?在什么时候为 Web 编写额外的复杂性会覆盖诸如易于部署和跨平台兼容性之类的好处，特别是如果您不想创建下一个 Stack Overflow，而只是构建一个内部应用程序?

Have Javascript libraries and advanced server side technologies made things such as right-click context menus, drag and drop, etc. doable on the client side without a large effort? At what point does the extra complexity of writing for the web override the benefits such as ease of deployment and cross-platform compatibility, particularly if you are not trying to create the next Stack Overflow, but instead just building an internal application?

内部应用程序的受众有限这一事实是否或多或少地覆盖了对胖客户端可以提供的改进可用性的任何担忧?

Does the fact that an internal application has a limited and captive audience more or less override any concerns over improved usability that a thick client can provide?

推荐答案

我不想的时候去 Web 应用程序:

I go Web app when I don't want to:

- 支持一千种环境，每个环境都有自己的怪癖.特别是病毒、特洛伊木马、软件干扰，并使其在任何地方都能正常工作.

- be supporting a thousand environments each with their own quirks. Specifically, viruses, trojans, software interfering, and making it work the same everywhere.

- 担心应用升级和接听大量电话

- 处理丢失数据的客户

当每笔交易的计算量很大，或者每笔交易有大量数据传输时，我会选择胖客户端.

I pick a thick client when the computation is intensive per transaction, or there is significant data transfer per transaction.

我喜欢通过一次升级解决每个人的问题.它可能不适合每个人，但它是我的生活质量和我工作的人的质量提升的地方.让一个网络应用在几个不同的浏览器上运行可能比在不同条件下运行大量不同的操作系统更容易.

I like fixing everyone's problems with one upgrade. It might not be for everyone, but it's where the quality of my life and those I work for goes up. Making a web app work on a few different browsers may be easier than a ton of different operating systems in different conditions.

随着 Flex/Air 的出现，您可以在浏览器中提供完整的应用程序体验.浏览器正在成为通用界面，无论是安装在本地还是在云端.

With the advent of Flex/Air you can provide an entire application experience in the browser. The browser is becoming the universal interface, whether it's installed locally or in the cloud.

Web 应用程序也有其缺点.我只是更有动力构建网络应用程序，因为对于我选择的项目来说，专业人士的优势似乎超过了劣势.

Web apps have their cons too. I just am more motivated to build web apps as the pro's seem to outweigh the cons for the projects I am choosing.

这篇关于什么时候应该构建 Web 应用程序与胖客户端?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！