RFB协议的实现 [英] Implementation of RFB protocol

问题描述

我要寻找的 RFB协议来使用它在我的项目，它长的搜索后的执行情况，我碰到这个的话题（答案是由一个专家成员的书面...）我已经发布一个主题另一个论坛上和我有同样的答案。

I am looking for an Implementation of the RFB protocol to use it in my project, after a long search about it, I came across this topic (the answer is written by an expert member ...) I already posted a topic on another forum and I had the same answer.

我的问题是：为什么我们称之为 RFB协议并没有一个API，或者实现它的库？
对于我所知，协议应该使用它的API;如TCP / IP，UDP ...

My question is: Why we call it RFB protocol and there is not an API or a library that implement it? For my knowledge, a protocol should have an API to use it; such as TCP / IP, UDP...

PS：我所张贴这里另一个问题>

PS: Another question posted by me about same problem here

推荐答案

一个协议，只需要一个描述被称为协议。例如， HTTP / 1.1协议是在RFC，这仅仅是文字的形式记录在案。是绝对的协议描述中没有的编程语言或API或图书馆的讨论。它是由不同的作者提供的API，这鼓励完全不同的实现，如<一个href=\"http://msdn.microsoft.com/en-us/library/windows/desktop/aa383630%28v=vs.85%29.aspx\">WinINet, 的libcurl 和的请求。

A protocol needs only a description to be called a protocol. For example, the HTTP/1.1 protocol is documented in the form of an RFC, which is just text. There is absolutely no discussion of programming languages or APIs or libraries in the protocol description. It is up to different authors to provide APIs, and this encourages wildly different implementations such as WinINet, libcurl, and Requests.

同样，RFB的协议的仅仅是一个两个软件组件是如何互相沟通和交流帧缓冲区的信息描述。协议描述的存在确实的不的暗示，因此必然成为你选择的编程语言的API或库。

Similarly, the RFB protocol is just a description of how two software components talk to each other and exchange frame buffer information. The existence of a protocol description does not imply that there must necessarily be an API or library for your chosen programming language.

这篇关于RFB协议的实现的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！