canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Loop/Architecture: Difference between revisions
→Desktop Client Architecture: Add link to room context information, and also create a new one for the data channels
(→Underlying Technologies: Update for current technologies) |
(→Desktop Client Architecture: Add link to room context information, and also create a new one for the data channels) |
||
| Line 74: | Line 74: | ||
== Address Book == | == Address Book == | ||
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. | See [[Loop/Architecture/Address Book]] for detail. | ||
== Room Contexts == | |||
Rooms may have context attached by the user. The context is stored as an encrypted data block on the server. | |||
See [[Loop/Architecture/Context]] for detail. | |||
== WebRTC Data Channels == | |||
The conversations set up between users may transmit data (e.g. text chat) via WebRTC data channels. There is a specified structure for this data. See [[Loop/Architecture/Data Channels]] for detail. | |||
= Mobile Client Architecture = | = Mobile Client Architecture = | ||