当你应该建立一个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.

有明显的情况下，其中一个应用程序应该是一个或另一个（例如不基于web的视频编辑软件）。在另一方面，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库和先进的服务器端技术制造的东西，如右键单击上下文菜单，拖放等在客户端可行没有大量的努力？在什么时候网络写作的额外的复杂性覆盖好处，比如易于部署和跨平台的兼容性，特别是如果你是不是想创建下一个堆栈溢出，而只是建立一个内部应用程序？

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?

推荐答案

我去网络应用的时候，我不想为：

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.

我想用一个升级修复了大家的问题。它可能不是适合每一个人，但它就是我的生活质量以及我工作的上升。使得在几个不同的浏览器的web应用程序的工作可能会比一吨在不同的条件下不同的操作系统的更容易。

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 /空气的出现则可以提供在浏览器整个应用程序体验。浏览器正在成为通用接口，无论是在本地还是在云中进行安装。

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应用程序如亲的似乎利大于弊因为我选择的项目。

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屋！