Skip to content

Commit 458c386

Browse files
acaohwillsonbenjie
authored
Add a note about the transport specification (graphql#1209)
* Add a note about the transport specification I'm seeing users and also the OSS community struggling at times to find the transport specification. Some have referred to this page in particular, so I'm hoping this leads them down the right path * Update src/content/learn/BestPractice-ServingOverHTTP.md Co-authored-by: Benjie <[email protected]> Co-authored-by: Hugh Willson <[email protected]> Co-authored-by: Benjie <[email protected]>
1 parent 5082f51 commit 458c386

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/content/learn/BestPractice-ServingOverHTTP.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,4 +82,9 @@ app.use('/graphql', graphqlHTTP({
8282
```
8383

8484
## Node
85+
8586
If you are using NodeJS, we recommend looking at the [list of server implementations](/code/#javascript-server).
87+
88+
## Draft Transport Specification
89+
90+
A detailed [HTTP & websockets transport specification](https://github.com/graphql/graphql-over-http) is in development. Though it is not yet finalized, these draft specifications act as a single source of truth for GraphQL client & library maintainers, detailing how to expose and consume a GraphQL API using an HTTP transport. Unlike the language specification, adherence is not mandatory, but most implementations are moving towards these standards to maximize interoperability.

0 commit comments

Comments
 (0)