oak-team/oak-gpui
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Distinguish between "foreground" and "background" RPC messages

Browse Source 
Some types of messages, which entail state updates on the host, should be
processed in the order that they were sent. Other types of messages should
not block the processing of other messages.

Co-Authored-By: Antonio Scandurra <me@as-cii.com>
This commit is contained in:
Max Brunsfeld
2022-02-16 10:01:23 -08:00
co-authored by Antonio Scandurra
parent 20858699bc
commit cf4291a126
2 changed files with 76 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files
crates/server/src/rpc.rs
+9 -3
View File
@@ -190,9 +190,10 @@ impl Server {
let type_name = message.payload_type_name();
log::info!("rpc message received. connection:{}, type:{}", connection_id, type_name);
if let Some(handler) = this.handlers.get(&message.payload_type_id()) {
let handle_message = (handler)(this.clone(), message);
let notifications = this.notifications.clone();
executor.spawn_detached(async move {
let is_background = message.is_background();
let handle_message = (handler)(this.clone(), message);
let handle_message = async move {
if let Err(err) = handle_message.await {
log::error!("rpc message error. connection:{}, type:{}, error:{:?}", connection_id, type_name, err);
} else {
@@ -201,7 +202,12 @@ impl Server {
if let Some(mut notifications) = notifications {
let _ = notifications.send(()).await;
}
});
};
if is_background {
executor.spawn_detached(handle_message);
} else {
handle_message.await;
}
} else {
log::warn!("unhandled message: {}", type_name);
}