# Chunked Protocol
The chunked protocol exists as an alterative to the websocket protocol. The chunked protocol comes in two sides, the read side and the write side. Usage of this protocol is discouraged, as development focuses on the websocket protocol.
Reading from the chunked protocol is done by requesting an http 1.1 GET to the endpoint,
TODO: Endpoint here. This request must contain the header
includes your client-id.
This will respond with an HTTP 1.1
Transfer-Encoding: chunked response. This response
has a cookie
muxy-connection-id that must be sent in the write requests.
This connection has the same authorization limits and semantics as the websocket connection.
This response will be filled, over time, with a series of null ('\0') terminated json blobs that are the same as the websocket responses.
Writing to the chunked protocol is done by making HTTP POST requests to the endpoint,
TODO: Endpoint here.
Write requests to this endpoint must contain the
muxy-connection-id cookie that was obtained
from the read request, and an authorization header in the form
authorization: <client-id> <jwt>.
To obtain an authorization JWT for use with this endpoint, use
TODO: Authorization flow here.
Requests to this endpoint have a body identical to the json blobs that the websocket API accepts. Each request to this endpoint must only have one json blob in the body.