Skip to content
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

Bi-Directional gateway #239

Open
wants to merge 8 commits into
base: next
Choose a base branch
from

Conversation

tomasz-blasz
Copy link
Contributor

  • Implement bi-directional Gateway for communication over WS with a platform.
  • Separate WS Channel logic from Transport abstraction.
  • Move Event logic into Gateway's Server
  • Separate Transport for uni-directional and bi-directional modes
  • Merge changes from 'next-bidirectional'
  • Fix reconnection feature after the Gateway abstraction was added

tomasz-blasz and others added 8 commits December 12, 2024 11:20
* feat: Modify openrpc gen for platform and app apis

* feat: Get dual openrpc generation somewhat working

* feat: Generate openrpc json
Merge next into next-bidirectional
Bidirectional is disabled by default. Can be in cmake: 'ENABLE_BIDRECTIONAL'.

UTs were executed with undefined UNIT_TEST.

SOME TESTS FAILED:
Test SubscribeDiscoveryOnNavigateToLaunchNotification failed:
  SubscribeDiscoveryOnNavigateToLaunchNotification failed. Error: 1
@rdkcmf-jenkins
Copy link

b'## Copyright scan failure
Commit: 432e68a
Report detail: https://gist.github.com/rdkcmf-jenkins/5ee8bd63ca5fbaf0645173f4ddb1f856'

@rdkcmf-jenkins
Copy link

b'## Blackduck scan failure details

Summary: 0 violations, 0 files pending approval, 1 file pending identification.

  • Protex Server Path: /home/blackduck/github/firebolt-openrpc/239/rdkcentral/firebolt-openrpc

  • Commit: 432e68a

Report detail: gist'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants