mirror of
https://github.com/microsoft/vscode.git
synced 2026-07-08 23:32:36 -05:00
4d882322ca
I want to use the rpc interface for communication via stdin/out in wsl, but currently RPC is tightly coupled to the control server. The control server also speaks msgpack instead of JSON, since it deals with binary messages. WSL won't, and we'll want to use JSON to interact with VS Code, so some separation is needed. This pulls out a base set of RPC types for use in both scenarios. Currently these are only 'helper' structs that don't actually do any i/o, but once I figure out the model I would like to have a cleaner way to do i/o in a unified way as well. For the control server, previously we basically handled all methods in one big `switch` block with nasty macros, whereas now there's nicer `register_a/sync` functions. Some additional small refactors were needed to preserve the strict ordering of server messages, since they need to be order else we get decompression errors. This is the `start_bridge_write_loop`. As a small benefit, this means we can avoid the relatively expensive async Tokio mutex that we were using, and instead use the standard library mutex.
22 lines
668 B
Rust
22 lines
668 B
Rust
/*---------------------------------------------------------------------------------------------
|
|
* Copyright (c) Microsoft Corporation. All rights reserved.
|
|
* Licensed under the MIT License. See License.txt in the project root for license information.
|
|
*--------------------------------------------------------------------------------------------*/
|
|
|
|
// todo: we should reduce the exported surface area over time as things are
|
|
// moved into a common CLI
|
|
pub mod auth;
|
|
pub mod constants;
|
|
#[macro_use]
|
|
pub mod log;
|
|
pub mod commands;
|
|
pub mod desktop;
|
|
pub mod options;
|
|
pub mod self_update;
|
|
pub mod state;
|
|
pub mod tunnels;
|
|
pub mod update_service;
|
|
pub mod util;
|
|
|
|
mod rpc;
|