Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

Implement ActionCable #1442

Merged
merged 2 commits into from
Jul 30, 2018
Merged

Implement ActionCable #1442

merged 2 commits into from
Jul 30, 2018

Conversation

BenEmdon
Copy link
Contributor

What

This PR implements ActionCable on client side in place of short polling. The backend ActionCable message broadcasting is already complete.


This closes #1395

@@ -158,14 +158,6 @@
location.href = success_path();
};

check_progress = function() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why don't we need this anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

check_progress would make a GET request to get the progress of the of the ongoing create and import. It would make this request continuously.
Instead of polling for the progress we are receiving the progress with ActionCable.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, 👍

@BenEmdon BenEmdon merged commit 973f8b8 into master Jul 30, 2018
@BenEmdon BenEmdon deleted the implement-actioncable branch July 30, 2018 17:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use ActionCable instead of short polling in setupv2
2 participants