-
Notifications
You must be signed in to change notification settings - Fork 2
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
Live sheet updates for viewers #53
Comments
It looks like Drive's push notifications are provided via webhook, which makes it a no-go. Basically our only real option is to just poll. Certainly doable, but much less fun.... |
Discovered https://zeit.co/now which has free hosting for OSS. We may be able to set up a server as a sort of web-push proxy instead of having to poll.... |
Changing the scope of this ticket. We may want to allow GMs to directly modify player sheets at some point, but that should be done later, as a separate ticket. Personally, I'm more excited for #69, which, combined with the Push channel established here, could allow for real time DM interactions. Part of that ticket is adding a new |
) * Add methods for collection the watch session API auth map Refs #53 * Import `http` from old branch; add `(create-session)` * Import updates to cljs-worker that fix CORS requests to push-server * Add events and fx to create and connect to sessions * Automatically create push sessions as the user navigates * Add some framework for dispatching push events * Reload sheets in response to "CHANGED" events Refs #53 It's happening! * Handle fatal server disconnects with exponential backoff retry Hopefully this will only come into play on local dev, but it's good to handle anyway, just in case. * Create shared throttle-with-set implementation Prep for `create-watches` routine, which we also want to throttle * Respond to `need-watch` events * Wait much longer between push/check when offline But check immediately when we come back online
We should be able to use the Drive API to get realtime updates to sheet data. Doesn't make sense until #25 is done, but once it is this would be pretty slick!
The text was updated successfully, but these errors were encountered: