GSoC: Add EmbeddedTransportBackend POC for iframe-less integration#124
Draft
mishraditi wants to merge 2 commits intojitsi:masterfrom
Draft
GSoC: Add EmbeddedTransportBackend POC for iframe-less integration#124mishraditi wants to merge 2 commits intojitsi:masterfrom
mishraditi wants to merge 2 commits intojitsi:masterfrom
Conversation
mishraditi
changed the title
mishraditi
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a proof of concept for the project I would like to work on, "External API without iframe." The
EmbeddedTransportBackendis a replacement forPostMessageTransportBackendthat lets both sides communicate through direct function calls instead of postMessage across an iframe. I am adding it here in js-utils because this is where the transport layer and the ITransportBackend interface already live, so it makes sense for this backend to sit alongside PostMessageTransportBackend.I have added tests so the behavior of the new backend is clear, how the pairing works, bidirectional messaging, dispose behavior, and also tests with the Transport class to show that events and request/response both work through it.