Registers handler to be called when eventname is triggered on this object. It will be called bound to this object.

As a side effect, if this is the first handler registered for the event type, it will be called with all previous triggers for this event. This allows event triggers to be queued before they are registered, as a convenience.

This is a helper on the constructor object to wait on the result of multiple promises. When all promises are fulfilled, the chain promise is fulfilled with an array of all the results in the same order as the promises were given.

It is called like this:

var wait - Promise.chain(promise1, promise2);
wait.then(function(results) {
    var result1 - results[0]
    ,   result2 - results[1]
    ;

    ...
});

Begins a transaction involving one or more stores. stores is the name of a single store or an array of store names. mode is optional, defaulting to "readonly".

Passing a mode of "readwrite" will create a transaction capable of creating or updating data in the contained stores.

If you do not need to group multiple operations in a transaction, the database will automatically create and commit appropriate single-operation transactions.

The Transaction API defines a Transaction.abort() method, and otherwise inherits the rest of the Database API defined here.

Use the transaction object immediately. It does not return a Promise, and the transaction will be committed as soon as no operations are being made against it. If you need to perform multiple operations on the transaction in sequence, rather than in parallel, you must perform each next operation in the success callback of the previous, or the transaction will close.

Important details on conflict resolution are described here. Read carefully.

If a remote API and database name are configured, fetch all new updates from the Sync server and apply them locally.

In the event of a conflict between an unsynced local change and a remote change being pulled, the "conflict" event will be triggered on the store containing the object.

The conflict event is given a put() callback, key, local value, and remote value, in that order. The conflict handler is responsible for saving any altered values or new keys as a result of the conflict, exclusively through the put() callback it receives.

If the handler saves any objects, these objects will be the sole results of the conflict and may not even include the original objects or keys at all. For example, two objects conflicting could result in a new merged object. If this is the case, you should push to share the results with the sync server.

If the handler does not save any objects, the default behavior is used and only the remote version is kept.

Important this is not reversable! This removes all local data!

Removes the local database entirely.

Important this is not reversable! This removes all local data!

Removes the local database entirely, then recreates it with the current schema and no data.

Access a named index, where query operations can be done against the indexed property.

The index is a version of the key using the indexed property as te key to identify stored objects by.

The indexed are defined as part of the schema during Database creation, can only be created or changed in schema upgrades, and they are only way to filter store contents by anything other than the key.

Request objects from the store, triggering an 'each' event on the promise for every object found. Does not collect the objects into any array. This method is memory efficient.

The filter parameter controls which objects are returned. The follow keys are allowed, including combinations.

gt

Only find keys greater than a given value

gte

Only find keys greater or equal to a given value

lt

Only find keys less than a given value

lte

Only find keys less than or equal to a given value

start

An index into the results to begin

stop

An index into the results to stop. The given index will not be included.

reverse

If true, the results will be given in reverse order

A non-object value for filter will find all objects with a key exactly equal to it.

Request an array of all objects in the store, accepting the same filter parameter as the walk() method above.

The result is an array of objects with key and value properties, with a single method next() which, if fetch() had been called with start and stop parameters, will fetch the next page of results.

Saves a value in the store, and fails if a value with the same key exists.

The new value is queued for the next push.

Saves a value in the store, and replaces any value currently stored at the same key.

The new value is queued for the next push.

If you need to update many objects together, this method is helpful. It takes an array of objects with key and value properties, and puts all of them into the store in a single transaction.

There is no varient to "add many", however.

If metavalue is missing, retreive the meta data associated with key named metaname. However, if metavalue is present, change the value for this meta data.

Any number of arbitrary meta fields may be associated with an object.

When the source store is updated, update the resutl set with new data.

The immediately parameter specifies if the results should be immediately refreshed to catch any changes made before it started watching, or should only update on the next update event. immediately defaults to true.

Repeat the query and update the results with current data.

The result set is only updated if the query succeeds.

Increase the limit on the number of results to object, and load the new items.

NOTE: Because this refreshes the query, even existing results from the original limit could change.

Shift to the next page of results, of the same length as the current.

Causes a NoSuchPage error, if this results in no data.

Shift to the previous page of results, of the same length as the current.

Causes a NoSuchPage error, if this results in no data.

The credentials will from this point forward authenticate API requests with themselves.

Credentials are used for all interactions with the Plasmid Sync service, including API calls to inspect the permissions a particular set of credentials has. For this reason, it may be common to make credential requests authenticated with another pair.

For example, an initial account is created for a user by creating their new Device Credentials with a pair of Bootstrap Credentials.

Self Credentials are both the actor and target of their own API calls.

Identifies the credentials as including a secret token, or only an access token.

Returns true or false.

Grant new permissions to these credentials.

This method is obviously useless for Self-authenticating Credentials, as they can only grant permissions they already have.

Any credentials may be grant any of their own permissions to another credentials pair.

Full explaination of permissions will be added in a separate document.

Creates a new set of credentials, and populates this object with the new access and secret.

For example, this would create a new Device Credential Pair, authenticated with Bootstrap Credentials capable only of creating new accounts.

bootstrap_credentials = new plasmid.Credentials({
    access: "guest-creator",
    secret: "knock-knock"
});
my_credentials = new Credentials({
    credentials: bootstrap_credentials,
});
my_credentials.create('guest')
.then(function(data) {
    console.log("I have a new access token: " + data.access);
    console.log("And a new remote database to sync with: " + data.dbname);
    console.log("But, I'm not telling you the value of data.secret");

    // Remember the credentials to re-use later, and set the new remote name

    self.meta.put('credentials', {
        access: data.access,
        secret: data.secret,
        dbname: data.dbname,
    });
    database.setRemote(data.dbname);
})