-
-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Where is the frame actually sent to client in code? #134
Comments
/*
rfbBool |
That is in rfbserver.c. HTH! |
Thanks for the recommendation. I see that the frames are sent in rfbWriteExact the socket.c, and that it will send the frame data in pieces, if we understand the method correctly. Is there a place where we can access the full frame that will be sent across? We are trying to generate a digest on the frame, and need access to the whole frame data. |
You mean contents of the whole framebuffer? That is almost never sent |
The partial updates are all I need. Basically, I would like the frame update data that is being sent to the client, whether its an rectangle, full frame, etc. Currently we are looking in rfbWriteExact, which stores the message buffer that will be sent, but that also includes header data. We would like to know where the frame is stored without the header data. Does that make more sense? Sorry for the confusion. Perhaps an explanation what I'm trying to do will help. I am trying to generate a sha256 digest on the frame data that are being sent to the client. There the client will also generate a digest, and send it back, for verification that the data being displayed on the client are correct. Once again, thanks for your help. |
Am Sun, 23 Oct 2016 15:21:05 -0700
You mean contents of the whole framebuffer? That is almost never sent |
I'm looking for away to generate a digest on the frame data that is sent to the client, before it is sent, but I cant seen to find where the data is stored and/or sent. Any help would be appreciated, Thanks.
The text was updated successfully, but these errors were encountered: