Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
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: Another question posted by me about same problem here
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.
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.