Loop/Architecture/MVP: Difference between revisions
< Loop | Architecture
Jump to navigation
Jump to search
(Created page with "[this is just a personal scratchpad right now; I'll be fleshing it out shortly] Based on the requirements for MVP, New architecture - Need to include flag that indicates aud...") |
No edit summary |
||
| Line 3: | Line 3: | ||
Based on the requirements for MVP, New architecture | Based on the requirements for MVP, New architecture | ||
* Need to include flag that indicates audio vs audio/video | |||
* Need to have WS connection to convey in-call information | |||
* Need shorter URLs / vanity URLs | |||
* Need means to update URL data (remote name, expiry) | |||
** Need different revocation behavior | |||
* Registration of user, phone # | |||
* Call URL for user, phone # | |||
* Updates to: | |||
** http://docs.services.mozilla.com/loop/apis.html | |||
* Identity | |||
* Different servers for different channels | |||
* Multiple incoming calls | |||
* Call forking | |||
* Call Progress | |||
* Timers | |||
** Server | |||
** Client | |||
Revision as of 18:01, 12 June 2014
[this is just a personal scratchpad right now; I'll be fleshing it out shortly]
Based on the requirements for MVP, New architecture
- Need to include flag that indicates audio vs audio/video
- Need to have WS connection to convey in-call information
- Need shorter URLs / vanity URLs
- Need means to update URL data (remote name, expiry)
- Need different revocation behavior
- Registration of user, phone #
- Call URL for user, phone #
- Updates to:
- Identity
- Different servers for different channels
- Multiple incoming calls
- Call forking
- Call Progress
- Timers
- Server
- Client