Operational transformation is a set of algorithms that allow you to sync documents. It's what Google Docs and Etherpad use for real-time collaboration. Gulf is a unixy ("do one thing and do it well") take on collaborative editing, by connecting documents with Node.js streams and employing OT to resolve conflicts automatically.
This project evolved from my determination to replace Etherpad with something better. Gulf was the smallest core of code that I felt comfortable extracting out of my prototypes. Unfortunately, I took a lot of detours before I could finish "something better" and eventually discovered something better than OT itself: CRDT. Gulf is thus relic, of sorts.
/*
* Server
*/
var textOT = require('ot-text').type
// Create a new master document
var doc = new gulf.Document({
storageAdapter: new gulf.MemoryAdapter,
ottype: textOT
})
doc.initializeFromStorage('abc') // Optionally supply default content
// Set up a server
ws.createServer(function(socket) {
// ... and create a slave link for each socket that connects
var slave = doc.slaveLink()
// now, add the new client as a slave
socket.pipe(slave).pipe(socket)
})
/*
* Browser
*/
var textOT = require('ot-text').type
// Create a new *editable* slave document (empty by default)
var doc = new gulf.EditableDocument({
storageAdapter: new gulf.MemoryAdapter,
ottype: textOT
})
// Implement editor bindings
doc._onBeforeChange = function() {/*...*/}
doc._onChange = function() {/*...*/}
doc._setContent = function() {/*...*/}
// Connect to alice's server
ws.connect(function(socket) {
// create a link to the master
var master = doc.masterLink()
// connect to master document
socket.pipe(master).pipe(socket)
})
And you have a collaborative editor!
A document may contain arbitrary data. The content of a document is available in myDocument.content (which is read-only!).
Now, how do I change this document if Document#content is untouchable? Well, thankfully there's also EditableDocuments.
Editable documents can be updated via the submitChange(cs) method. The cs is short for changeset. A changeset contains the changes to a document.
EditableDocuments leave some methods for you to implement:
var document = new gulf.EditableDocument(adapter, ottype)
document._onChange = function(cs, cb) {
/*
apply changes
return promise
*/
}
document._setContent = function(newcontent, cb) {
/*
set new content
return promise
*/
}
document._onBeforeChange = functioncb() {
/*
collect changes and submitChange() them
return promise
*/
}
Before anything can happen, the editable document is initialized wwith _setContent.
Everytime the document is changed by an incoming edit _onChange is called with the changeset.
Before an incoming edit is processed _onBeforeChange is called, allowing you to save possible changes before the new edit is applied. Just like you'd git commit before git pulling anything -- we don't want things would get hairy.
There are two ways to get a changeset: 1) you compute a diff between the last known state and the current one. 2) You record edit events and turn them into a changeset. There are editors which provide changesets out-of-the-box, others will have to be persuaded (using diff computation).
Ok, now we update our editable document and we notice that it keeps a record of all revisions -- documents remember every change ever done. Nice.
Now, Alice and Bob each have an editable document and want to sync them. For this, we need some kind of mediator document that takes care of the syncing process and represents the absolute truth. In gulf this mediator is called the master document. It has the final say in which edit is accepted and how the edits are ordered.
Now, somehow Alice and Bob need to link their documents to that master document in order to send it the changes they make.
For this gulf provides, surprise, Links. A Link is a simple DuplexStream. If Alice wants to connect to the master document, she creates a master link to it. The master document attaches Alice's link as a slave link.
net.createserver((socket) => {
socket.pipe(masterDoc.slaveLink()).pipe(socket) // for each socket
}).listen(1234)
net.connect(1234,function(er, socket) {
socket.pipe(slaveDoc.masterLink()).pipe(socket)
})
A document can have many slaves, but only one master link (EditableDocuments have no slave links).
Now that we've connected all documents, every time Alice or Bob make a change the edits will just flow to the other documents.
You can sync any document type you have an ot type implementation and an editor for.
Since adding gulf syncing to an editor is a repetitive task and hard to get right (what with selection retention, generating diffs, etc.) there are ready-made bindings for you!
The following bindings are available:
If you want to create a binding yourself, please follow the API of the existing modules (ie. expose a single class extending EditableDocument and taking an additional option called editorInstance. And don't forget to implement EditableDocument#close()!). Also, make sure to name the npm package like this: gulf-editor-your-name-here
Gulf allows you to store your data anywhere you like, if you can provide it with a storage adapter. It comes with an in-memory adapter, ready for you to test your app quickly, but when the time comes to get ready for production you will want to change to a persistent storage backend like mongoDB or redis.
Currently implemented adapters are:
If you'd like to write your own storage adapter, head on to the API docs below and be sure to name it like this: gulf-backend-your-name-here
It's probably easiest to observe gulf in action. So, have a look at these examples.
Additions wanted: If you have the perfect example show-casing gulf or its related libraries leave me a note via email or the issues.
Instantiates a new link, optionally with some options:
opts.credentials The credentials to be sent to the other end for authentication purposes.opts.authenticate A functon which gets called with the credentials from the other side and has the following signature: (credentials): Promise<Object>opts.authorizeWrite A function which gets called when the other end writes a message, and has the following signature: (msg, user): Promise<Bool>; user is the value returned by your authenticate hook.opts.authorizeRead A function which gets called when this side of the link writes a message, and has the following signature: (msg, user): Promise<Bool>; user is the value returned by your authenticate hook.The return value of opts.authenticate is also used as the author field when saving snapshots.
Here's an example of how to setup link authentication and authorization:
var link = new gulf.Link({
authenticate: function(credentials) {
return authenticate('token', credentials)
.then((user) => {
return user.id
})
}
, authorizeWrite: function(msg, userId, cb) {
switch(msg[0]) {
case 'edit':
return authorize(userId, 'document:change')
.then(auth => auth.granted)
case 'requestInit':
return authorize(userId, 'document:read')
.then(auth => auth.granted)
}
}
, authorizeRead:function(msg, userId, cb) {
switch(msg[0]) {
case 'init':
case 'edit':
return authorize(userId, 'document:read')
.then(auth => auth.granted)
case 'ack':
return authorize(userId, 'document:change')
.then(auth => auth.granted)
}
}
})
Fired when the document has received an init message containing a snapshot, has reset the history and set the new contents.
Fired when an edit has been committed (confirmed with master, applied locally and stored). ownEdit tells you if edit was submitted by this document or was received from a different document.
Instantiates a new, empty Document. storageAdapter is optional and defaults to a new instance of gulf.MemoryAdapter
Loads a document from the storage. opts will be passed to the Document constructor.
Creates a link with opts passed to the Link constructor and attaches it as a slave link.
Creates a link with opts passed to the Link constructor and attaches it as a master link.
Attaches an existing link as master.
Attaches an existing link as a slave.
Listener function that gets called when a link attached to this document receives an init message. data could look like this: {contents: 'abc', edit: '<Edit>'}
A listener function that gets called when a link receives an edit message. Adds the edit to the queue (after checking with a possible master) and calls Document#dispatchEdit() when ready.
Checks with the document's History whether we know this edit already, and if not, whether we know its parent. If so, it calls Document#sanitizeEdit(), applies the edit to this document with Document#applyEdit(), add it to this document's History, send's an ack message to the link the edit came from, distributes the edit to any slaves and emits an edit event.
Transforms the passed edit against missed edits according to this document's history and the edit's parent information.
Applies an edit to the document's content.
Sends the passed edit to all attached links, except to fromLink.
This class extends gulf.Document and overrides some of its methods.
The following are the defaults for the options (just mergeQueue at this time):
{
mergeQueue: true // If gulf should merge multiple outstanding edits into one, for faster collaboration.
}
Fired when gulf has received the init packet and has set the contents via EditableDocument#_setContent.
Fired when an edit has been committed (confirmed with master, applied locally and stored). ownEdit tells you if edit was submitted by this document or was received from a different document.
Update an editable document with local changes provided in changes. This wraps the changes in an Edit and sends them to master.
Fired when EditableDocument#update() has been called, but before the changes have been approved by the master. edit is the newly created Edit.
Note: If queue merging is enabled, the supplied edit may be merged with other outstanding edits before being sent to the server. Thus, if queue merging is enabled, it is not guaranteed that you will get a commit event for every edit that you got an update event for.
An EditableDocument consumer can call this to tear down the connection between EditableDocument and editor.
Needs to be implemented by you or by wrappers (see Editor bindings). Is called after the document has been initialized with _setContents for every change that is received from master.
Needs to be implemented by you or by wrappers (see Editor bindings). Is called if the document receives an init message or to reset the document in case of an error.
Needs to be implemented by you or by wrappers (see Editor bindings). Is called right before _onChange() is called to keep track of any outstanding changes.
instantiates a new edit without parent, changes or id. Thus it's pretty useless.
Deserializes an edit that was serialized using gulf.Revision#toJSON().
Creates a new initial edit. Initial revisions carry content but no changes.
Creates a new edit with changes set to cs.
Applies this edit on a document snapshot.
transforms this edit against the passed one and sets the other as this edit's parent. (This operation rewrites history.)
transforms this edit against the passed one and without resetting this edit's parent.
merges the passed edit with this one. Returns the new edit.
Serializes this edit.
Returns a new edit instance that has exactly the same properties as this one.
Gulf storage adapters are provided in npm packages that are named gulf-backend-yournamehere.
They deal with revision objects.
A revision is an object that looks like this:
{
id: 48
, changeset: [0, "h"]
, parent: 47 // ID of this revision's parent
, content: '"Hello world"' // stringified representation of the new contents
, author: 12 // The id of the author, as returned by `opts.authenticate` in the Link options (or the value you passed to gulf.Document#receiveEdit, if you passed in the edit directly)
}
If you're having trouble writing your own adapter, check out the in-memory adapter and the blob store adapter.
To run the tests in node and the browser, run the following:
npm run build && npm run test-local
(Make sure to open the provided link in the browser of your choice.)
(c) 2013-2016 by Marcel Klehr
GNU Lesser General Public License
v5.0.0
v4.1.0
editableInitializedcommitmergeQueuev4.0.5
v4.0.4
v4.0.3
v4.0.2
v4.0.1
v4.0.0
FAQs
transport-agnostic operational transformation control layer
We found that gulf demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.