-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Irmin graphql subscriptions (take 2) #616
Conversation
9ac3919
to
cf5a5a5
Compare
I'm not quite sure why Appveyor cannot find Otherwise, this PR should be ready for review. |
Any idea why the |
I think the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
One question since I'm not all that familiar with how subscriptions work: it looks like unwatch
will be called automatically when the client unsubscribes, but how does the client send the actual unsubscribe request?
The client sends a |
cf5a5a5
to
ad937bb
Compare
I'm not sure either. It's green now without any relevant changes on my part. I did rebase on master though. |
Yeah, I'm not sure what's going on with the tests 😕 |
The PR description of andreas/ocaml-graphql-server#141 unintendedly closed #598 with no option of reopening, so this PR is a copy of #598 😒
This PR adds the ability to watch the entire store or a specific key with notifications delivered via the GraphQL subscription mechanism (currently only websockets, possibly Server-Sent Events or chunked HTTP responses in the future).
Adding
Irmin_unix.set_listen_dir_hook ()
tocli.ml
may be required...