Allow the specification of the KaleidoscopeEvent creation date/time.
This allows Sites and Venue to emit their recent history to a Core when
connecting to populate the Core with their content upon arrival.
- Integrated EventEmitter2 for async event processing
- Changed jshint reporter module URL to avoid use of SSH
- Core can disconnect a service node, generates many events
- Service Node can disconnect a Core, generates many events
Nothing yet processes those events. Many things need to be cleaned up
and removed based on a Core Node disconnection. The Core itself needs to
remove all Kaleidoscope events and other data received from the Service
Node, and the Service Node needs to remove all CoreUser records (and
everything they did while there).
That's going to take a minute to implement throughout all the systems.
The better approach in ExpressJS is to author up a quick middleware you
can toss onto any route to short-circuit the rest fo the route with the
redirect.
The implementation submitted was actually running double output. The
"checkForUser" method would call `res.redirect`, return, and then the
method would continue and produce additional output.
Explicit middleware helps prevent those kinds of errors :)
Alternative to error page before:
`Cannot read properties of undefined (reading '_id')` during checking `!res.locals.post.author._id.equals(req.user._id)` in line 268.
rob
CyberShell