# RFC: Streams support - fragmented response

**URL:** <https://discuss.jsonapi.org/t/rfc-streams-support-fragmented-response/852>\
**Category:** Uncategorized\
**Created:** [November 28, 2016, 10:23pm UTC](https://discuss.jsonapi.org/t/rfc-streams-support-fragmented-response/852 "2016-11-28T22:23:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrmod](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/chrmod/32/359_2.png) [@chrmod](https://discuss.jsonapi.org/u/chrmod)\
**Post date:** [November 28, 2016, 10:23pm UTC](https://discuss.jsonapi.org/t/rfc-streams-support-fragmented-response/852/1 "2016-11-28T22:23:07Z")

</div>

As [Streams](https://streams.spec.whatwg.org/) are getting forward through standardization - JSON API may consider alternative format for Fetching Data response, that will utilize streaming capabilities of the browsers.

ReadableStream could go though response having every record separated via new line, which would allow progressive content loading for large responses or at low connectivity.

Possible fragmentation may look something like that:

```
HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{ "links": { "self": "http://example.com/articles" }, "data": [
{ "type": "articles", "id": "1", "attributes": { "title": "JSON API paints my bikeshed!" } }, 
{ "type": "articles", "id": "2", "attributes": { "title": "Rails is Omakase" } }
]}

```

Is that a direction worth consideration?