Closed
Bug 971990
Opened 10 years ago
Closed 10 years ago
Client needs to register with simple push server
Categories
(Hello (Loop) :: Client, defect, P1)
Hello (Loop)
Client
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla33
backlog | mlp+ |
People
(Reporter: abr, Assigned: standard8)
References
Details
(Whiteboard: [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework][p=0, s=mlpnightly1, 1.5;p1, ft:webrtc][qa+])
No description provided.
Reporter | ||
Updated•10 years ago
|
Component: General → Client
Comment 1•10 years ago
|
||
Client needs to obtain a simple push URL from the simple push server.
Assignee | ||
Updated•10 years ago
|
Comment 2•10 years ago
|
||
Mark -- I'm assigning this to you as part of bug 974875. Thanks.
Assignee: nobody → standard8
Assignee | ||
Updated•10 years ago
|
Whiteboard: [blocked by Simple Push]
Assignee | ||
Updated•10 years ago
|
Priority: -- → P1
Assignee | ||
Updated•10 years ago
|
Whiteboard: [blocked by Simple Push] → [blocked by Simple Push][temp workaround is bug 981064]
Comment 3•10 years ago
|
||
Yesterday we decided to use SimplePush with websocket as described here: https://gist.github.com/matzew/cbda360d72eaaef75971
Assignee | ||
Updated•10 years ago
|
Whiteboard: [blocked by Simple Push][temp workaround is bug 981064] → [chrome implemented with a workaround for demo, may need rework]
Assignee | ||
Comment 4•10 years ago
|
||
(In reply to Rémy Hubscher (:natim) from comment #3) > Yesterday we decided to use SimplePush with websocket as described here: > https://gist.github.com/matzew/cbda360d72eaaef75971 We've done a workaround based on this use of websockets in chrome code. This may need rework later depending on what happens re chrome versus content privs.
Assignee | ||
Updated•10 years ago
|
Priority: P1 → P2
Assignee | ||
Updated•10 years ago
|
Whiteboard: [chrome implemented with a workaround for demo, may need rework] → [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework]
Updated•10 years ago
|
backlog: --- → mlp+
Assignee | ||
Updated•10 years ago
|
Updated•10 years ago
|
Whiteboard: [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework] → [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework][p=0, 1.5;p1, ft:webrtc]
Updated•10 years ago
|
Priority: P2 → P1
Target Milestone: --- → mozilla32
Assignee | ||
Comment 5•10 years ago
|
||
The remaining work here is being done in bug 1000007.
Updated•10 years ago
|
Whiteboard: [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework][p=0, 1.5;p1, ft:webrtc] → [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework][p=0, s=mlpnightly1, 1.5;p1, ft:webrtc]
Assignee | ||
Updated•10 years ago
|
Target Milestone: mozilla32 → mozilla33
Marking verified based on prior smoketesting.
Status: RESOLVED → VERIFIED
QA Contact: anthony.s.hughes
Whiteboard: [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework][p=0, s=mlpnightly1, 1.5;p1, ft:webrtc] → [landed on loop-ui-inital][chrome implemented with a workaround for demo, may need rework][p=0, s=mlpnightly1, 1.5;p1, ft:webrtc][qa+]
You need to log in
before you can comment on or make changes to this bug.
Description
•