Keyman LMLayer prototype

Prototype of NRC language model layer for Keyman.

I'm developing and experimenting with the API and how different API designs will practically work.

Current status (Tue Oct 2 09:45:10 MDT 2018):

• Developing communication protocol between keyboard and Web Worker.

Communication protocol between keyboard and asynchronous worker

We have decided that everything to the right of the KeymanWeb will be in a Web Worker. However, communication can happen only through postMessage(data) commands, where data is a serializable object (via the structured clone algorithm).

What serializable object can we send that will adhere to the open-closed principle?

Messages

The idea is to use a discriminated union. The protocol involves plain JavaScript objects with one property called message that takes a finite set of string values.

These string values indicate what message should be sent. The rest of the properties in the object are the parameters send with the message.

{
    message: 'predict',
    // message-specific properties here
}

See also: XML-RPC

Messages are not methods. That is, there is no assumption that a client will receive a reply when a message is sent. However, some pairs of messages, such as predict and suggestions, lightly assume request/response semantics.

Tokens

Tokens uniquely identify an input event, such as a keypress. Since Keyman should ask for an asynchronous prediction on most keypresses, the token is intended to associate a prediction and its response with a particular input; Keyman is free to ignore prediction responses if they are for outdated input events.

The Token type is opaque to LMLayer. That is, LMLayer does not inspect its contents; it simply uses it to identify a request and pass it back to Keyman. There are a few requirements on the concrete type of the Token:

1. Tokens MUST be serializable via the structured clone algorithm;
2. Tokens MUST be usable as a key in a Map object.
3. Tokens MUST be unique across messages. That is, tokens MUST NOT be duplicated for between different messages.

It is up to Keyman to create unambiguous tokens that can be uniquely identified through the round-trip process.

In the following examples, I'll use the subset of number values that are interpretable as 31-bit signed integers.

Example

An asynchronous message to predict after typing 'D':

{
    message: 'predict',

    token: 1,
    transform: {
        insert: 'D',
        deleteLeft: 0,
        deleteRight: 0
    },
    contexts: [
        // TO BE DETERMINED
    ]
}

Message types

Currently there are three message types:

Message	Direction	Parameters	Expected reply	Uses token
ready	LMLayer → keyboard	configuration	No	No
predict	keyboard → LMLayer	transform, contexts	Yes — suggestions	Yes
suggestions	LMLayer → keyboard	suggestions	No	Yes

Message: ready

Must be sent from the LMLayer to the keyboard when the LMLayer's model is finished initializing. It will send configuration, which is a plain JavaScript object requesting configuration from the keyboard.

The keyboard SHOULD NOT send any messages to the LMLayer before it receives the ready message.

There are only two options defined so far:

let configuration = {
    /**
     * How many UTF-16 code units maximum to send as the context to the
     * left of the cursor ("left" in the Unicode character stream).
     *
     * Affects the `context` property sent in `predict` messages.
     *
     * TODO: Will this ever bisect graphical cluster boundaries?
     */
    leftContextCodeUnits: 32, 

    /**
     * How many UTF-16 code units maximum to send as the context to the
     * right of the cursor ("right" in the Unicode character stream).
     *
     * Affects the `context` property sent in `predict` messages.
     *
     * TODO: Will this ever bisect graphical cluster boundaries?
     */
    rightContextCodeUnits: 32, 
};

TODO

• make TinyWorker's self inherit from the global scope?
• write documentation for new initialization messages
• make simple index.html that demos a dummy model
• enable continuous integration
• TypeScript!
• Figure out what a Context will be
• Refactor LMLayer with state pattern?