You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Took me awhile to digest a way to do this and not a lot of usage to pull from.
I came across graphql-subscription-server which uses graphqlws to hook into the subscribing and publishing in a way that allows you to use it configure it like a pubsub.
I was able to eventually use a similar approach to publish events that are matches to listening subscriptions and it works well, but unfortunately I haven't found a way to defer the subscription and connection state to something else (i.e. Redis).
It would be great to extend this capability so that I don't lose connection state if I lose the process, deploy, etc.
Activity
EIrwin commentedon Dec 15, 2019
Took me awhile to digest a way to do this and not a lot of usage to pull from.
I came across graphql-subscription-server which uses
graphqlwsto hook into the subscribing and publishing in a way that allows you to use it configure it like a pubsub.I was able to eventually use a similar approach to publish events that are matches to listening subscriptions and it works well, but unfortunately I haven't found a way to defer the subscription and connection state to something else (i.e. Redis).
It would be great to extend this capability so that I don't lose connection state if I lose the process, deploy, etc.