Closed
Bug 985387
Opened 11 years ago
Closed 10 years ago
Loop Server — A new registration to an existing User Device (login) should add a new SimplePush URL if it is not already stored
Categories
(Hello (Loop) :: Server, defect)
Hello (Loop)
Server
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rhubscher, Assigned: alexis+bugs)
References
Details
(Whiteboard: [qa+])
Attachments
(1 file)
No description provided.
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 1•11 years ago
|
||
Well actually, there is two things :
- For now, we handle only a Simple Push URL per user (since user are cookies based)
- We want to manage a Simple Push URL per User Device (assuming we are using FxA or MSISDN for logging.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 2•11 years ago
|
||
there is actually no reason that we have only one simple push url per user. Even with sessions, we could have more than one simple push url if needed.
This will let us have multiple simple push urls per user for free as soon as we activate a different authentication scheme.
Reporter | ||
Comment 3•11 years ago
|
||
Well we still need to define how we can identify user devices then because we want to store a simple push url per user device.
Assignee | ||
Comment 4•11 years ago
|
||
Yes, that's true. And that's why it could make sense to have the client sending us an unique ID it generates when starting up loop for the first time.
Adam, any feedback about that?
Flags: needinfo?(adam)
Comment 5•11 years ago
|
||
(In reply to Alexis Metaireau (:alexis) from comment #4)
> Yes, that's true. And that's why it could make sense to have the client
> sending us an unique ID it generates when starting up loop for the first
> time.
>
> Adam, any feedback about that?
Yes, once we go to account-based identification, we're going to want endpoint identifiers for managing push URLs. So, where the current schema contains a single push URL, and Fernando's proposed schema contains a list of push URLs (possibly with attached attributes), what we really want is something that maps from an endpoint ID to its associated push URL (this is, as far as I can tell, basically what you're proposing).
Flags: needinfo?(adam)
Updated•10 years ago
|
Summary: Loop Server — A new registration to an existing User Device should replace the existing SimplePush URL. → Loop Server — A new registration to an existing User Device (login) should add a new SimplePush URL if it is not already stored
Updated•10 years ago
|
Whiteboard: [qa+]
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → alexis+bugs
Assignee | ||
Comment 6•10 years ago
|
||
Attachment #8446603 -
Flags: review?(tarek)
Updated•10 years ago
|
Attachment #8446603 -
Flags: review?(tarek) → review+
Assignee | ||
Comment 7•10 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•