# Frames

> No tag: the server opens the channel once the acceptor took the connection; the connector answers with everything it sends to the acceptor, one client frame per channel response, and its channel response finish hangs up.

Canonical: https://protocol.diverge.network/2.3.0/endpoints/daemons-connect/server/frames/
Specification revision: 2.3.0

The server opens this channel when the acceptor takes the connection,
after the byte `0` on the scope. What arrives on it is everything the
connector sends to the acceptor.

- **The request.** The channel request carries nothing.
  [Request](/2.3.0/endpoints/daemons-connect/server/frames/request/) states
  its form.
- **The response.** The frames the connector sends, as channel
  responses, each one client frame, and the channel response finish,
  which hangs up.
  [Response](/2.3.0/endpoints/daemons-connect/server/frames/response/)
  states the sequence.
- **What the server does with it.** The server relays each channel
  response onto the acceptor's half of the connection as one channel
  response, in order, and finishes the acceptor's half when the
  channel finishes. The server reads none of them.
- **One channel.** The server opens exactly one frames channel on a
  connect scope, and none on a scope it answered with an error.