Glass needs to handle a lot of data. Almost all of which comes from Proximity in the JSON:API format. A feature of this format is that every request has exactly the same structure, with only the data differing. Following the JSON:API format has many benefits, but one of its drawbacks is the fact that JSON:API messages contain a lot of boilerplate (informationless structure). Because glass has to handle a lot of data, this boilerplate can increasingly slow down our requests the more data is transmitted (compared to raw information). What I would like to propose is the supporting of compressed messages by proximity, an optional feature that strips these responses from their boilerplate, allowing us to sidestep some transmission overhead.
I think that this could be achieved within a cycle of 4 weeks. In proximity we would have to setup a system to compress the data and in glass we would have to setup one to decompress it. The comp