v0.1.1

• #12 - Fix bug where graphql subscription clients that had sent identical graphql-ws start messages would receive too many messages

Use subscription resolvers

This release is not backward compatible, but I expect that this new API will be what we stick with.

• #10 - You no longer need to make an EPCPPublisher and use EPCPPubSubMixin. Instead you use a WebSocketOverHttpPubSubMixin in your graphql resolvers. Subscription resolvers are now used instead of ignored.

v0.0.2

• #1 - GraphqlWsOverWebSocketOverHttpExpressMiddleware responds to graphql-ws stop messages by telling GRIP gateway to unsubscribe from relevant channel
• #2 - GraphqlWsOverWebSocketOverHttpExpressMiddleware responds with Keep-Alive-Interval response header so that WebSocket-Over-HTTP gateway makes keepalive requests every 120 seconds (configurable).
• #3 - subscriptions-transport-ws-over-http responds to WebSocket-Over-HTTP close events by deleting all subscriptions for that connection and unsubscribing gateway from relevant gripChannels
• Add travis-ci