# Stop

> The client ends the tree by opening one channel on the scope; the server sends nothing on the channel and answers with the response finish of the scope.

Canonical: https://protocol.diverge.network/2.3.0/container-proxy-endpoints/filesystem-tree/client/stop/
Specification revision: 2.3.0

The client ends the tree by opening one channel on the scope, as
[Channels](/2.3.0/frames/channels/) provides. The channel request is the
stop. The server sends no frame on the channel; the response finish of
the scope is its answer.

- **The request.** The payload of the channel request is empty. Every
  channel request the client sends on this scope is the stop,
  whatever its payload. [Request](/2.3.0/container-proxy-endpoints/filesystem-tree/client/stop/request/) states
  its form.
- **The response.** The server sends no channel response and no
  channel response finish on the channel. It sends no response on
  the scope after it receives the stop, and it sends the response
  finish of the scope. [Response](/2.3.0/container-proxy-endpoints/filesystem-tree/client/stop/response/) states
  the sequence.
- **One channel.** A second channel request on the scope has the
  effect of the first and no other effect.
- **The filesystem.** The stop does not alter the filesystem of the
  container, or any other tree on the connection.