LO Event running TODO

Nobody has claimed this yet.

Start by reviewing the remaining checklist, especially queue.js, lo_event.js:init(), storage imports, and the node environment mentioned in the issue. Break the open items into separately scoped tasks, then use the existing event pipeline and node tests to verify each selected behavior is implemented without the listed errors.

Written by the indexing model from the issue text.

The LO Event package has been abstracted out, but there may be work left to do. Please leave any bugs, things not yet implemented, or other ideas in this issue.

Ajax logger
Opt in/out strategy
Add ability to specify which verbs, nouns, etc. we might use in the protocol in some kind of header (e.g. register our schema)
Fix and test queue.js within a node environment
Fix auto-increment within queue.js (currently resets to 0 each time)
Ensure all events have event field - Websocket's onclose and onerror do not
Implement blacklisting server side, test overall pipeline
Update server-side code to handle lock_fields, metadata, auth, etc.
Disable ability to send/store events if we are getting more than some number of exceptions
Resolve any storage errors when importing lo_event in another non-extension node project Uncaught TypeError: _storage_js__WEBPACK_IMPORTED_MODULE_0__.storage.get is not a function
We want to be able to fetch the websocketServer from storage
Add ability to specify util.backoff termination policy (do we just (1) die or (2) continue retrying using the last delay amount)
Consider structing / destructing in lo_event.js:init()

Assessment

Research direction

Description

Contributor guide

First steps

More from ArgLab/writing_observer

Similar issues