Loop/Architecture: Difference between revisions
< Loop
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
=== User Generates "Call-Me" URL === | === User Generates "Call-Me" URL === | ||
[[File:loop-create-call-me.png|center|"Call-Me" URL Generation]] | |||
=== Non-User Clicks "Call-Me" URL === | === Non-User Clicks "Call-Me" URL === | ||
[[File:loop-use-call-me.png|center|"Call-Me" URL Activation]] | |||
=== User Accepts Call === | === User Accepts Call === | ||
[[File:loop-answer-call.png|center|Call Answered]] | |||
=== User Rejects Call === | === User Rejects Call === | ||
[[File:loop-reject-call.png|center|Call Rejected]] | |||
=== User Blocks "Call-Me" URL === | === User Blocks "Call-Me" URL === | ||
[[File:loop-block-url.png|center|"Call-Me" URL Blocked]] | |||
=== User Calls Other User === | === User Calls Other User === | ||
[[File:loop-call-user.png|center|Loop user calls other Loop user]] | |||
= Client Architecture = | = Client Architecture = | ||
Revision as of 15:26, 18 March 2014
Design Goals
Underlying Technologies
Mozilla Technologies
The Loop project relies on a number of other technologies under development within Mozilla. These include the following:
Third-Party Technologies
- Node.js for Loop server, at least through production
Open Issues
These technology choices will be moved into one of the preceding sections as decisions are made:
- Localization (bug 972884)
- Client MVC Library + associated libs (bug 975548)
- Client side unit-testing framework (bug 976127)
- Standalone-page unit-testing framework (bug 976133)
- Client-driven end-to-end framework (bug 976114)
- Standalone-page end-to-end system testing framework (bug 976134)
- Client CSS toolkit (if any) (bug 976854)
- Standalone-page CSS toolkit (if any) (bug 976857)
Network Architecture
Data Flows
User Connects
User Generates "Call-Me" URL
Non-User Clicks "Call-Me" URL
User Accepts Call
User Rejects Call
User Blocks "Call-Me" URL
User Calls Other User
