Skip to content

feat: add repeater connection progress events and request ID tracking #20

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.

Sign up for GitHub

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

Jump to bottom
Merged
dustinmcafee merged 1 commit into from
Dec 30, 2025
Merged

feat: add repeater connection progress events and request ID tracking #20

dustinmcafee merged 1 commit into from
Dec 30, 2025

Conversation

@dustinmcafee
Copy link
Collaborator

@dustinmcafee dustinmcafee commented Dec 15, 2025 •
edited
Loading 

feat: add ContinuousUpdates extension and repeater progress events

ContinuousUpdates Extension (RFC 6143):
- Add pseudo-encoding -313 for client capability advertisement
- Send EndOfContinuousUpdates (msg 150) when client advertises support
- Handle EnableContinuousUpdates message to enable/disable push updates
- When enabled, server pushes updates without FramebufferUpdateRequest
- When disabled, use traditional request-response model

Repeater Progress Events:
- Add RfbMessageSent event (emitted when RFB ID sent to repeater)
- Add HandshakeComplete event (emitted when VNC handshake completes)
- Add request_id tracking for correlating connection events
- Add connect_repeater_with_request_id() and connect_repeater_with_progress()

Both features maintain backward compatibility with existing APIs.

@dustinmcafee dustinmcafee added the enhancement New feature or request label Dec 15, 2025
@dustinmcafee dustinmcafee linked an issue Dec 15, 2025 that may be closed by this pull request
feat: add ContinuousUpdates Extension and repeater connection progress events and request ID tracking #19
Closed
@dustinmcafee
feat: add ContinuousUpdates extension and repeater progress events
de5618d 
ContinuousUpdates Extension (RFC 6143):
- Add pseudo-encoding -313 for client capability advertisement
- Send EndOfContinuousUpdates (msg 150) when client advertises support
- Handle EnableContinuousUpdates message to enable/disable push updates
- When enabled, server pushes updates without FramebufferUpdateRequest
- When disabled, use traditional request-response model

Repeater Progress Events:
- Add RfbMessageSent event (emitted when RFB ID sent to repeater)
- Add HandshakeComplete event (emitted when VNC handshake completes)
- Add request_id tracking for correlating connection events
- Add connect_repeater_with_request_id() and connect_repeater_with_progress()

Both features maintain backward compatibility with existing APIs.
@dustinmcafee dustinmcafee force-pushed the feat_19 branch 2 times, most recently from 9ba0981 to de5618d Compare December 18, 2025 02:51
@dustinmcafee dustinmcafee merged commit ecad3d5 into main Dec 30, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Neustradamus Neustradamus Awaiting requested review from Neustradamus

Assignees

@Neustradamus Neustradamus

@dustinmcafee dustinmcafee

Labels

enhancement New feature or request

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

feat: add ContinuousUpdates Extension and repeater connection progress events and request ID tracking

3 participants

@dustinmcafee @Neustradamus