Confirmed users
632
edits
Loop/Architecture: Difference between revisions
Jump to navigation
Jump to search
→Address Book
(Link ID architecture proposal) |
|||
| Line 61: | Line 61: | ||
the main means by which users are expected to initiate Loop calls on desktop is via the "Address Book" sidebar, which will contain a list of the user's contacts. For the initial versions of Loop, contacts will can be populated from several sources, via a one-way synchronization (that is, the data will be imported from a remote authority and updated from that remote authority, but cannot be changed by the Loop client). A necessary implication of this setup is that all contacts will need to track which data source they belong to, and be updated only from those sources. | the main means by which users are expected to initiate Loop calls on desktop is via the "Address Book" sidebar, which will contain a list of the user's contacts. For the initial versions of Loop, contacts will can be populated from several sources, via a one-way synchronization (that is, the data will be imported from a remote authority and updated from that remote authority, but cannot be changed by the Loop client). A necessary implication of this setup is that all contacts will need to track which data source they belong to, and be updated only from those sources. | ||
See [[Loop/Architecture/Address Book]] for detail. | |||
= Mobile Client Architecture = | = Mobile Client Architecture = | ||