From 00a75257f9dd6ef683721e777ed646880218e879 Mon Sep 17 00:00:00 2001 From: Rikki Schulte Date: Wed, 23 Feb 2022 09:37:35 +0100 Subject: [PATCH 1/2] 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 --- src/content/learn/BestPractice-ServingOverHTTP.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/learn/BestPractice-ServingOverHTTP.md b/src/content/learn/BestPractice-ServingOverHTTP.md index a67e896e7b..d629867c26 100644 --- a/src/content/learn/BestPractice-ServingOverHTTP.md +++ b/src/content/learn/BestPractice-ServingOverHTTP.md @@ -83,3 +83,7 @@ app.use('/graphql', graphqlHTTP({ ## Node If you are using NodeJS, we recommend using either [express-graphql](https://github.com/graphql/express-graphql) or [apollo-server](https://github.com/apollographql/apollo-server). + +## Draft Transport Specification + +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 are being treated as a single source of truth by graphql client & library maintainers from across language communities for how graphql protocols work. Unlike the language specification, adherence is not mandatory for interoperability, but most implementations are moving towards these standards. From 5cb4e3064b4821595d7cd1f290d84091cfcbd393 Mon Sep 17 00:00:00 2001 From: Hugh Willson Date: Sun, 13 Nov 2022 19:52:57 -0500 Subject: [PATCH 2/2] Update src/content/learn/BestPractice-ServingOverHTTP.md Co-authored-by: Benjie --- src/content/learn/BestPractice-ServingOverHTTP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/learn/BestPractice-ServingOverHTTP.md b/src/content/learn/BestPractice-ServingOverHTTP.md index d629867c26..f72bc69943 100644 --- a/src/content/learn/BestPractice-ServingOverHTTP.md +++ b/src/content/learn/BestPractice-ServingOverHTTP.md @@ -86,4 +86,4 @@ If you are using NodeJS, we recommend using either [express-graphql](https://git ## Draft Transport Specification -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 are being treated as a single source of truth by graphql client & library maintainers from across language communities for how graphql protocols work. Unlike the language specification, adherence is not mandatory for interoperability, but most implementations are moving towards these standards. +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.