zed/crates/collab
Antonio Scandurra fb2590d913 Use a FuturesUnordered to process foreground messages
This prevents deadlocks when e.g., client A performs a request to client B and
client B performs a request to client A. If both clients stop processing further
messages until their respective request completes, they won't have a chance to
respond to the other client's request and cause a deadlock.

This arrangement ensures we will attempt to process earlier messages first, but fall
back to processing messages arrived later in the spirit of making progress.
2022-06-22 15:04:17 +02:00
..
k8s Move prometheus annotations from deployment to pod spec 2022-06-10 14:32:36 -07:00
migrations Register projects in the database and record worktree extensions 2022-06-21 10:29:26 +02:00
src Use a FuturesUnordered to process foreground messages 2022-06-22 15:04:17 +02:00
.env.template.toml Add affordance to copy user's invite link if they have a code 2022-05-19 17:57:46 -06:00
basic.conf Rename zed-server to collab 2022-04-09 08:30:42 -06:00
Cargo.toml Accept a datetime range when querying project activity 2022-06-21 14:03:10 +02:00
Procfile Rename zed-server to collab 2022-04-09 08:30:42 -06:00
README.md Remove more files supporting the old web front-end 2022-04-21 09:06:34 -06:00

Zed Server

This crate is what we run at https://collab.zed.dev.

It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://zed.dev, which is a separate repo running on Vercel.