opencoweb / coweb-jsoe Goto Github PK

See opencoweb/coweb#229

Also see coweb-jsoe/examples/possible_bug/buggy.js

The documentation is out of sync with the OTEngine public API. One example is the order of arguments for OTEngine.remoteEvent. These need to be addressed.

When using syncInbound and syncOutbound, the OTEngine does not create the ContextVector object correctly - the ContextVector's internal array is actually set to a reference to another ContextVector, but since JavaScript allows accessing undefined attributes, this was never detected until manual examination.

This issue will track updating the directory layout to organize source files, build/release files (zip files, etc), documentation, examples, and other files.

Organization

/bin - scripts for generating release builds, etc
/build - contains release zip files, etc
/src - source code
/docs - documentation
/examples - example usage programs

If I want to put coweb across two servers for HA or to load balance is that possible? Do you have anything planned for this?

PS Greetings form the Etherpad community, we're looking at possibly using your engine for a new drawing tool we're working on

When I purposely use the same global order, I expect for the engine (HistoryBuffer specifically) to crash reporting a duplicate global order, but this does not happen. The code should not be reporting false negatives.

It might be useful to have a Node.js package accessible from Node Package Manager (npm) for application developers to easily integrate the OT JavaScript engine into their application. This issue investigates the feasibility (and possible implementation) of doing so.