PART 5: Implement full bi-directional communication over WebSocket/LP/SSE

[kris-lab]

SO WE HAVE:

• STREAMING FROM ELASTICFEED TO THE JS-CLIENT
• POSSIBILITY TO TRIGGER EVENT ON CHANNEL LEVEL, FEED LEVEL, ENTRY LEVEL

TO DO: see related feedlabs/sdk-js#10

• SEND REQUESTS FROM JS-CLIENT TO ELASTICFEED
  • ACTION: MORE DATA, INIT DATA ETC.
  • METRICS:
    • SAVE ENTRY: ACTIONS, HABITS, BEHAVIOURS ETC
    • SAVE VIEW: BEHAVIOURS
  • DATA: SAVE CONENT FOR ENTRY
• STATE ENGINE
  • LIST OF FEEDs with binded SOCKETs (optimization); cluster ready
• AUTHENTICATION
  • FOR FEED ACCESS
• SERVICES
  • API STORAGE END-POINT
  • STREAM BI-POINT
  • METRICS END-POINT
• PLUGIN MANGER
  • PROFILER
  • RESOURCE API
• WORKFLOW MANAGER

[kris-lab]

To many unrelated changes. Must be merged.

• added plugin upload
• added plugin CLIENT-SERVER communication over RPC
• add example plugin which start at engine start and communicate over Unix ports
• improved workflow concepts

[kris-lab]

Follow up #37