host/com.erfangholami.androidsolidservices.host.binder

Package-level declarations

Types

class AuthenticatorBinder(session: HostSession, grants: AppGrantStore, guard: AccessGuard, scope: CoroutineScope, dispatcher: CoroutineDispatcher = Dispatchers.IO, readyTimeoutMillis: Long = DEFAULT_READY_TIMEOUT_MILLIS) : IASSAuthenticatorService.Stub

The IASSAuthenticatorService binder: sign-in state, the calling app's own grant, and revocation of that grant by the app itself.

DataModulesBinder

class DataModulesBinder(contactsDataModule: SolidContactsDataModule, ticketsDataModule: SolidTicketsDataModule, guard: AccessGuard, moduleRoots: ModuleRootResolver, scope: CoroutineScope, dispatcher: CoroutineDispatcher = Dispatchers.IO) : IASSDataModulesService.Stub

The IASSDataModulesService binder, hosting the contacts and tickets module interfaces.

NotificationsBinder

class NotificationsBinder(notificationsManager: NotificationsManager, guard: AccessGuard, scope: CoroutineScope, dispatcher: CoroutineDispatcher = Dispatchers.IO) : IASSNotificationsService.Stub

The IASSNotificationsService binder. The inbox belongs to the account, so every verb is checked on the whole pod: reads at VerbAccess.INBOX_READ, deletions at VerbAccess.INBOX_WRITE, and anything that speaks to another inbox as the user, or records a decision, at VerbAccess.INBOX_SEND. The acting account is the first WebID each verb takes.

ResourceBinder

class ResourceBinder(resourceManager: SolidResourceManager, session: HostSession, guard: AccessGuard, scope: CoroutineScope, spoolDirectory: File, dispatcher: CoroutineDispatcher = Dispatchers.IO) : IASSResourceService.Stub

The IASSResourceService binder: the full resource surface, each verb guarded on the resource it names at the level VerbAccess gives it.

SharingBinder

class SharingBinder(sharingManager: SharingManager, guard: AccessGuard, scope: CoroutineScope, dispatcher: CoroutineDispatcher = Dispatchers.IO) : IASSharingService.Stub

The IASSharingService binder. Every verb needs VerbAccess.SHARE: on the resource it names when it names one, otherwise on the whole pod, because the share indexes and the received-shares list belong to the account, not to any one resource.