Loop client should be pluggable

RESOLVED WONTFIX

Status

P5
enhancement
Rank:
55
RESOLVED WONTFIX
5 years ago
3 years ago

People

(Reporter: alexis+bugs, Unassigned)

Tracking

unspecified
Points:
---
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [triage])

(Reporter)

Description

5 years ago
Currently, loop client (in firefox and in the webapp) relies on opentok.

The code should be made pluggable so it allows the client to use a different implementation than tokbox;

This is specifically important as the code tokbox provides isn't open source, and relies heavily on their infrastructure.

WebRTC is a technology that allows to do p2p communications, that would be too bad to let the signaling part of firefox loop be provided *only* by a specific partner.
Severity: normal → enhancement
backlog: --- → -
Blocks: 1024548
See Also: → bug 1024548
No longer blocks: 1024548

Updated

4 years ago
Rank: 55
Flags: firefox-backlog+
Priority: -- → P5
Whiteboard: [triage]
We're not going to be able to do anything in this area in any known timescale
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.