OlegIlyenko

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

• query
• mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

philips

#!/bin/bash

source /etc/environment
name=$(cat /etc/machine-id)

if [ ! -f /opt/consul ]; then
        mkdir /opt
        mkdir /var/lib/consul
        curl http://storage.googleapis.com/ifup-org-tilde/consul-0.2.0-linux-x86-64.lzma | lzcat > /opt/consul
        chmod +x /opt/consul

nullstyle

require 'rubygems'
require 'typhoeus'


Typhoeus::Request.get("http://msn.com")  #succeeds
Typhoeus::Request.post("http://msn.com") #segfault