# Use an unbounded channel for peer's outgoing messages · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/d4fe1115e7cdfe79de7fdb86a7a384c3800225cc)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: d4fe1115e7cdfe79de7fdb86a7a384c3800225cc

Requested commit: d4fe1115e7cdfe79de7fdb86a7a384c3800225cc

Commit: d4fe1115e7cdfe79de7fdb86a7a384c3800225cc

Tree: 282b0af2d8185f1970eb8ec3722f031cf731bb64

Author: Max Brunsfeld

Committer: Max Brunsfeld

## Message

```
Use an unbounded channel for peer's outgoing messages

Using a bounded channel may have blocked the collaboration server
from making progress handling RPC traffic.

There's no need to apply backpressure to calling code within the
same process - suspending a task that is attempting to call `send` has
an even greater memory cost than just buffering a protobuf message.

We do still want a bounded channel for incoming messages, so that
we provide backpressure to noisy peers - blocking their writes as opposed
to allowing them to buffer arbitrarily many messages in our server.

Co-Authored-By: Antonio Scandurra <me@as-cii.com>
Co-Authored-By: Nathan Sobo <nathan@zed.dev>

```

## Parents

- [82afacd33da576602018413fac39ca9334992d38](https://git.cafe/gitcafe/zed/commit/82afacd33da576602018413fac39ca9334992d38?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/d4fe1115e7cdfe79de7fdb86a7a384c3800225cc?format=markdown)