Use binary message RPC protocol for plugin API #41
Conversation
This file contains 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
The commit fixes a minor typo in the `description` field for the `StrictSSL` cli option. Signed-off-by: Prajwal Borkar <prajwalborkar5075@gmail.com>
tortmayr
force-pushed
the
plugin-rpc-v2
branch
3 times, most recently
from
390e06d
to
9a15846
Compare
Refactors the plugin RPC protocol to make use of the new message-rpc introduced with eclipse-theia#11011/eclipse-theia#11228. - Refactor plugin-ext RpcProtocol API to reuse the new message-rpc protocol - Remove custom RPC message encoding and handling reuse message-rpc - Implement `QueuingChannelMultiplexer` that queues messages and sends them accumulated on the next process.tick (replaces the old Multiplexer implementation) - Refactors proxy handlers and remote target handlers - Use `Channel` instead of `MessageConnection` for creating new instances of RPCProtocol - Refactor `RpcMessageEncoder`/`RpcMessageDecoder` to enable overwritting of already registered value encoders/decoders. - Add mode property to base `RpcProtocol` to enable switching from a bidirectional RPC protocol to a client-only or server-only variant. - Implement special message encoders and decoders for the plugin communication. (Replacement for the old `ObjectTransferrer` JSON replacers/revivers) - Adapt `HostedPluginServer` and `HostedPluginClient` API to send/receive messages in binary format instead of strings. This enables direct writethrough of the binary messages received from the hosted plugin process. - Adapt `hosted-plugin-process` and `plugin-host` to directly send binary messages via `IpcChannel`/`BinaryMessagePipe` - Remove incorrect (and unused) notification proxy identifiers and instantiation - NotificationExt was instantiated in the main context - There were unused notification proxy identifiers for main and ext in the wrong contexts Part of eclipse-theia#10684 Fixes eclipse-theia#9514 Contributed on behalf of STMicroelectronics Co-authored-by: Lucas Koehler <lkoehler@eclipsesource.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What it does
Refactors the plugin RPC protocol to make use of the new message-rpc introduced with eclipse-theia#11011/eclipse-theia#11228.
Refactor plugin-ext RpcProtocol API to reuse the new message-rpc protocol
QueuingChannelMultiplexerthat queues messages and sends them accumulated on the next process.tick (replaces the old Multiplexerimplementation)
Channelinstead ofMessageConnectionfor creating new instances of RPCProtocolRpcMessageEncoder/RpcMessageDecoderto enable overwritting of already registered value encoders/decoders.RpcProtocolto enable switching from a bidirectional RPC protocol to a client-only or server-only variant.Implement special message encoders and decoders for the plugin communication. (Replacement for the old
ObjectTransferrerJSON replacers/revivers)Adapt
HostedPluginServerandHostedPluginClientAPI to send/receive messages in binary format instead of strings. This enables direct writethrough of the binary messages received from the hosted plugin process.Adapt
hosted-plugin-processandplugin-hostto directly send binary messages viaIpcChannel/BinaryMessagePipeRemove incorrect (and unused) notification proxy identifiers and instantiation
Part of eclipse-theia#10684
Fixes eclipse-theia#9514
Co-authored-by: Lucas Koehler lkoehler@eclipsesource.com
Contributed on behalf of STMicroelectronics
How to test
Review checklist
Reminder for reviewers