graphql-over-http
graphql-over-http copied to clipboard
graphql
Working draft of "GraphQL over HTTP" specification
I have a question regarding how the response protocol is determined for a request that could POTENTIALLY result in multiple payloads. ## Scenario: client sends header `accept: multipart/mixed` with non-"Incremental...
Is it worth mentioning batch requests? In this case, an array of objects is transmitted via http.
It's come up a number of times in our discussions as a working group: We would like to have optional features that can be adopted and if adopted by a...
Research some other serialization formats and whether they have implications for content-types / status codes. For example, the usual case that we consider is GraphQL over HTTP with JSON as...
For GraphQL over HTTP it would be great to standardize few of the directives for describing HTTP metadata. These directives would be useful both for documentation and run time enforcement;...
[Server-sent events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events) are a perfect mechanism for informing a GraphQL client that the schema has been updated. They don't require the complexity of websockets, and they are uni-directional. I'm proposing...
The draft spec currently requires that UTF-8 is the one and only encoding supported by servers. See: > If the media type in a `Content-Type` or `Accept` header includes encoding...
Would it make sense to create a collection of HTTP requests that represent common combinations of header values, validation failures, etc. and their expected status code / response headers according...
If the client issues `Accept: application/graphql-response+json, application/json` and the server does not support this for the request (e.g. the request uses `@stream`/`@defer` so needs a multipart response) then the server...