История

Mark Hammond 55982952d1 Add extra logging to the tabs engine to help diagnose strange problems syncing tabs		2024-10-28 22:00:38 +00:00
..
android	Switch to UniFFI library mode	2024-09-18 20:31:35 +00:00
src	Add extra logging to the tabs engine to help diagnose strange problems syncing tabs	2024-10-28 22:00:38 +00:00
Cargo.toml	support: Extract `payload_support::try_fit_items`.	2024-07-09 20:03:09 +00:00
README.md	Rename `master` to `main` in many places	2020-06-29 08:43:33 -07:00
build.rs	Updating UniFFI to version 0.23	2023-01-27 12:38:55 -05:00
uniffi.toml	Build improvements with UniFFI library mode	2024-10-17 17:59:42 +00:00

README.md

Synced Tabs Component

Implementation Overview

This crate implements an in-memory syncing engine for remote tabs.

Directory structure

The relevant directories are as follows:

src: The meat of the library. This contains cross-platform rust code that implements the syncing of tabs.
ffi: The Rust public FFI bindings. This is a (memory-unsafe, by necessity) API that is exposed to Kotlin and Swift. It leverages the ffi_support crate to avoid many issues and make it more safe than it otherwise would be. It uses protocol buffers for marshalling data over the FFI.
android: This contains android bindings to synced tabs, written in Kotlin. These use JNA to call into to the code in ffi.
ios: This contains the iOS binding to synced tabs, written in Swift. These use Swift's native support for calling code written in C to call into the code in ffi.

Features

Synchronization of the local and remote session states.

Business Logic

Storage

The storage is all done in memory for simplicity purposes. The host applications are free to persist the remote tabs list if it makes sense to them.

Payload format

Every remote sync record is roughly a list of tabs with their URL history (think of the back button). There is one record for each client.

Association with device IDs

Each remote tabs sync record is associated to a "client" using a client_id field, which is really a foreign-key to a clients collection record. However, because we'd like to move away from the clients collection, which is why this crate associates these records with Firefox Accounts device ids. Currently for platforms using the sync-manager provided in this repo, the client_id is really the Firefox Accounts device ID and all is well, however for older platforms it is a distinct ID, which is why we have to feed the clients collection to this Tabs Sync engine to associate the correct Firefox Account device id.

Getting started

Prerequisites: Firefox account authentication is necessary to obtain the keys to decrypt synced tabs data. See the android-components FxA Client readme for details on how to implement on Android. For iOS, Firefox for iOS still implement the legacy oauth.

Platform-specific details:

Android
iOS: start with the guide to consuming rust components on iOS

API Documentation

TODO