Subscription support

With graphql-core v0.4.9, schemas now support subscriptions. I added support in epoxy for them https://github.com/graphql-python/graphql-epoxy/commit/70e8b9592b7af04a929004d76ddcef5b8b9c6a83 should be same level of difficulty in graphene.

[ghost]

@femesq Sure, that makes sense. Anything that would add/modify/delete data is grounds for a triggered event, but there’s a key distinction to be made here, which is that if you place the trigger event on a mutation, then if I understand you, that means that only mutations that happen through GraphQL will trigger that event. That means things like the django admin, or command line scripts that may run (scheduled cron jobs or other events), unless those are all modified to use graphql, will not cause the event to happen.

If, on the other hand, the event happens post-save on the model, then as long as the django ORM was involved, it will trigger.

re: permissions, I wasn’t actually suggesting this was a problem, but it’s a situation where an example would be useful. The important thing here is to not tie permissions too closely to the framework. It should be up to developer how they want to check for permissions, but we want an example that’s beyond “broadcast to everyone”.

[lightning18]

How does this work? How do you trigger a push from the server? The way I understand the commit is that this is just the subscription part and I have to manually implement a pub-sub, am I right?