Skip to content
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.

Sign up for GitHub

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

Jump to bottom

figure out how to not rely on WebSocket server after RTC upgrade #14

Open
cvan opened this issue Mar 17, 2015 · 2 comments
Open

figure out how to not rely on WebSocket server after RTC upgrade #14

cvan opened this issue Mar 17, 2015 · 2 comments
Labels
enhancement question

Comments

@cvan
Copy link
Owner

cvan commented Mar 17, 2015

No description provided.

@potch
Copy link
Collaborator

potch commented Apr 6, 2015

We actually don't presently rely on the server post-upgrade except for there's logic to repair the connection. We could refactor the code to only re-connect if we are a) relying on ws for messaging fallback (a la iPhone) or if the WebRTC connection breaks.

@cvan
Copy link
Owner Author

cvan commented Apr 7, 2015

correct.

relevant commits:
a1f2871
b2b226b

@cvan cvan closed this as completed Apr 7, 2015
@cvan cvan reopened this Apr 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cvan @potch