术语“在客户端呈现的 UI”和“在客户端呈现的 UI”之间有什么区别？和“..在服务器端”？
术语“在客户端呈现的 UI”和“..在服务器端”之间有什么区别？
有技术示例吗？
- UI 客户端 = ?
- UI 服务器端 = ?
不仅是网络开发很糟糕，我想服务器端不会呈现任何内容？
What is the difference between the term "UI that gets rendered on client side" and "..on server side "?
Any examples of technologies ?
- UI Client Side = ?
- UI Server Side = ?
not only web development sucks I guess that nothing ever gets rendered on the server side ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我假设一个网络环境。
客户端
使用 javascript 创建最终 DOM 的页面，即客户端呈现。以 GWT 为例。一般情况下的 AJAX。
如果您使用 Flash，您还可以使用客户端渲染。该插件是最吸引人的。
它们都在客户端加载某种逻辑，从服务器检索数据，然后决定在页面中显示哪些具体数据（每个名称、数字、日期等）。加载到客户端的代码（javascript、flash）不会因使用而改变。
服务器端
服务器端将通过 JSP 页面（或任何技术）来创建最终的 HTML。无论如何，浏览器是渲染的，但是“有 5 个客户端，因此每个姓氏有五行”这一决定是在服务器端而不是客户端做出的。
I assume a web envorinment.
Client side
A page that uses javascript to create the final DOM, its client side rendering. GWT by example. AJAX in general.
If you use Flash you also use client-side rendering. The plugin is the one drawing all.
They both load some kind of logic at the client, retrieve data from server and then decide what concrete data to display (each name, number, date, etc) in the page. The code loaded into the client (the javascript, the flash) doesn't change from use to use.
Server side
Server side will be a JSP page (or any technology) to create a final HTML. Anyway the browser is the one who renders, but the decision "there are 5 clients so there are five rows one with each LastName" is taken at server side, not client side.
如果您谈论的是 Web 环境，那么：
服务器端 指的是在服务器上（例如在 ASP.NET 中）生成并发送到 Web 浏览器的任何 html。这可能是网页的大部分内容。
客户端是指在浏览器中运行并从那里更改页面 html 的任何内容。一般来说，这意味着一旦网页文档 (DOM) 已经位于 Web 浏览器中，Javascript（带有一个或多个 Javascript 库，例如 jQuery）就会对其进行操作。
举个例子，在“Ajax”的世界中，这通常意味着服务器呈现初始网页，但是客户端上的JavaScript然后修改网页响应用户输入（可能实际上在幕后与服务器进行了通信），而无需实际将整个页面发送回服务器以重新呈现。
If you are talking about a web environment, then:
Server Side refers to any html that is generated on the server (e.g. within ASP.NET) and sent to the web browser. This is probably most of the web page.
Client side refers to anything that runs in the browser and changes the page's html from there. Generally, this means Javascript (with one or more Javascript library such as jQuery) manipulating the web page document (DOM) once it is already in the web browser.
As an example, in the world of "Ajax", this often means that the server renders the initial web page, but that javascript on the client then amends the web page in response to user input (probably having actually communicated with the server behind the scenes), without having to actually post the whole page back to the server to have it re-rendered.
我相信，对于被归类为“渲染”的客户端/服务器来说，它必须涉及基于某些输入的某种形式的计算，以产生用于查看或打印的输出。除此之外，我们还必须看看相对而言正在完成多少工作才能产生输出。
因此，我不会将通过网络连接输出像素数据的服务器归类为渲染了任何内容，除非它做了一些工作来获取这些像素。例如，通过管道传回位图的 Web 服务器尚未呈现任何内容。但是，正在流回实时计算机桌面的终端服务器却可以。
最好考虑应用程序示例并尝试根据客户端/服务器来描述这些示例。
读取数据库并显示其数据的桌面应用程序正在呈现客户端。
从服务器下载顶点数据的 Direct3d 游戏是客户端
但是，如果顶点数据是动态的，并且服务器必须做一些计算来提供它，那么你也可以认为正在发生客户端+服务器渲染。
网页几乎总是客户端+服务器的混合体，尤其是那些基于 Asp.Net、JSP 或 PHP 的网页；由于页面输出是动态的，因此 HTML 必须先由服务器“呈现”，然后再由客户端呈现。
很难为任何单一技术提供具体答案。
Windows Forms、Direct3D、OpenGL、iPhone 等、Flash、Pure WPF、Silverlight 以及所有其他工具都能够成为纯客户端 UI 以及混合体 - 取决于应用程序。
然而，我想您可能会争辩说，不存在纯粹的服务器端 UI 之类的东西（迫不及待地等待能够指出这一点的人发表评论！）
I believe that for a client/server to be classed as 'rendering' something it must involve some form of calculation based on some input to produce output that is intended for viewing or printing. Beyond that we then have to look at how much work is being done, relatively speaking, in order to produce the output.
So, I would not class a server that pumps out pixel data via a network connection as having rendered anything unless it's done some work to get those pixels. E.g. a Web Server piping back a bitmap hasn't rendered anything. But a terminal server that is streaming back a live computer desktop has.
It's best to think of Application Examples and try to describe those in terms of client/server.
A Desktop App that reads a database and displays its data is rendering client-side.
A Desktop App that employs some form of parameterised XML template-based UI that is stored in a database and retrieved (and formatted) by a stored procedure could be argued to be client and server.
A Direct3d game that downloads vertex data from a server is client-side
However, if the vertex data is dynamic, and the server has to do some calculations to serve it up, then you could also argue client + server rendering is taking place.
Web pages are nearly always a mix of client + server, especially those based on Asp.Net, JSP or PHP for example; since the page output is dynamic and therefore the HTML has to be 'rendered' by the server before then being rendered by the client.
It's difficult to provide concrete answers for any sole technology.
Windows Forms, Direct3D, OpenGL, iPhone et al, Flash, Pure WPF, Silverlight and all the rest are all capable of being pure client-side UI, and a mix - depending on the application.
I suppose you could argue, however, that there is no such thing as a pure server-side UI (can't wait for a comment from someone who can point to one!)
我认为这种意义上的渲染=创建一些“我应该显示什么”数据的过程，而不是“我应该显示什么”到显示器上显示的光栅图像的实际转换。
I suppose that rendering in this meaning = process of creation some 'what should I display' data, not the actual conversion of 'what should I display' to raster image shown on display.