All Classes and Interfaces

Class
Description
Default implementation for DittoDependencies which creates a ditto directory inside the directory provided.
Ditto is the entrypoint for accessing Ditto-related functionality in the Java SDK.
Builder to construct a new Ditto instance.
 
An address uniquely representing another device on the Ditto network.
How often to transmit Bluetooth LE advertisements.
How much power to use when transmitting Bluetooth LE advertisements.
Represents an attachment and can be used to insert the associated attachment into a document at a specific key.
The different events that can occur in relation to an attachment fetch.
Event signaling the completion of an attachment download.
Event signaling the deletion of an attachment.
Event signaling download progress for an attachment.
 
The different types of DittoAttachmentFetchEvent.
Serves as a token for a specific attachment that you can pass to a call to DittoStore.fetchAttachment(com.ditto.java.DittoAttachmentToken, com.ditto.java.DittoAttachmentFetchEventHandler).
Provides feedback to the developer about Ditto authentication status.
Provides info about the authentication status.
Log in to a remote authentication service, using an OnlineWithAuthentication or an Online identity.
 
 
 
 
 
 
 
A store observation listener is called whenever an active store observer receives a new query result.
A store observation listener is called whenever an active store observer receives a new query result.
 
Specific servers that Ditto should attempt to connect to.
 
Represents a connection between two peers in a Ditto mesh network.
Contains information about a remote peer that has requested a connection.
Indicates whether a connection request should be authorized.
The type of DittoConnection between two DittoPeers signaling what transport is being used.
Container for a number.
An interface describing the dependencies required to initialise a Ditto instance.
Entrypoint for accessing information about the amount of disk storage used by Ditto.
 
A directory or file in the Ditto working directory.
An identifier for Ditto documents.
Provides an interface to specify a path to a key in a document identifier that you can then call a function on to get the value at the specified key as a specific type.
All errors that are thrown by the Ditto SDK are wrapped as a DittoError.
 
The possible underlying reasons an DittoError.ActivationError occurs.
The provided license token has expired.
The provided license token is in an unsupported future format.
Verification of the provided license token failed.
The Ditto instance has not yet been activated, which is achieved via a successful call to Ditto.setOfflineOnlyLicenseToken(String).
 
The possible underlying reasons an DittoError.AuthenticationError error occurs.
Failed to authenticate with remote server.
Represents a fatal error that the Ditto instance cannot recover from.
Errors related to IO devices.
The possible underlying reasons an DittoError.IoError occurs.
An I/O operation failed because the specified entity (such as a file) already exists.
An I/O operation failed because the specified entity (such as a file) already exists.
An I/O operation failed.
An I/O operation failed because the necessary privileges to complete it were not present.
Outstanding usage of ditto's working directory detected when trying to instantiate a new Ditto, which would have led to concurrent usage of the backing database files.
Errors transforming Ditto mesh presence data to or from JSON encoding.
The possible underlying reasons a DittoError.PresenceError occurs.
Parsing presence JSON failed.
Generating presence JSON failed.
 
The possible underlying reasons a DittoError.StoreError occurs.
The target file for the attachment copy already exists.
The attachment data failed to be retrieved.
The attachment file failed to be copied.
The given attachment file could not be found.
The attachment could not be found.
The attachment could not be found.
The attachment token was invalid.
An error occurred with the storage backend (LMDB).
A generic CRDT error occurred.
The provided document content failed to be encoded.
The document could not be found.
The attachment copy failed.
A problem occurred creating the attachment.
A Counter couldn't be created from the decoded Map.
Data could not be decoded.
The document could not be decoded.
The value could not be decoded.
The provided value could not be encoded.
A problem occurred fetching the attachment.
The document's data at the specified path could not be obtained.
The document ID's data at the specified path could not be obtained.
The directory that Ditto attempted to use for its persisted data could not be initialized.
An invalid CRDT type was encountered.
The document's internal representation was invalid.
The live query has not obtained a valid identifier.
An invalid value was encountered for a corresponding CRDT type.
The document did not have an _id key when attempting to decode it.
The document, represented as a CBOR map, had a key that was not a string.
The provided query arguments were invalid
Compilation of the provided query failed.
The query was invalid.
The query is invalid.
The query is syntactically valid but uses features that are either not supported at all yet or not supported in a particular context.
 
The possible underlying reasons a DittoError.TransportError error occurs.
Decoding of transport diagnostics data failed.
The wrong platform's DittoTransportConfig was provided.
Some not-yet-categorized error occurred.
Operation is not supported.
 
Errors interacting with DittoSmallPeerInfo.
Invalid base64-encoded string:
If the amount of JSON data is too nested according to our self-imposed limits, or if the data cannot be parsed to determine the depth.
The observability subsystem is unavailable.
Expected valid CBOR.
Expected valid JSON.
The given Map was missing a required entry for the given key name.
The value provided was not a Map.
The object is or contain(s) types that aren't JSON compatible.
The size of the provided metadata is too large.
The provided DittoSmallPeerInfoSyncScope value didn't correspond with any known enum cases.
Enum for the type of file represented by a DittoDiskUsageItem.
Settings not associated with any specific type of transport.
 
 
 
The various identity configurations that you can use when initializing a Ditto instance.
A manually-provided certificate identity.
Develop peer-to-peer apps with no cloud connection.
Test a Ditto Cloud app with weak shared token authentication ("Playground mode").
Run Ditto in secure production mode, logging on to Ditto Cloud or on on-premises authentication server.
A mode where any device is trusted provided they know the secret key.
 
 
Configure this device as a Ditto server.
 
 
 
Main access for Ditto logging API.
 
 
Singleton with static methods to customize the logging behavior from Ditto.
 
Container for a number that can be incremented and decremented.
Represents a mutable CRDT register that can be updated while updating a document.
An instance of Ditto taking part in the mesh network.
Configuration of peer-to-peer transports, which are able to discover and connect to peers on their own.
 
 
 
 
The entrypoint for all actions that relate presence of other peers known by the current peer, either directly or through other peers.
 
 
Represents the Ditto mesh network of peers and their connections between each other.
Represents results returned when executing a DQL query containing a DittoQueryResultItem for each match.
Represents a single match of a DQL query, similar to a "row" in SQL terms.
Container for a number.
 
Entrypoint for small peer info collection.
 
Provides access to execute Ditto queries.
A store observer invokes an observation handler whenever results for its query change.
Provides access to sync related functionality of Ditto.
A sync subscription configures Ditto to receive updates from remote peers about documents matching the subscription's query.
 
 
 
 
A configuration object specifying which network transports Ditto should use to sync data.