Billet Connection Issues

[AThilenius]

On an unreliable network (where the WebSocket is dropped a lot), the terminal will just stop responding until the page is refreshed. I think this is just a callback issue. The keystrokes are getting to Billet, just not from Billet (or maybe not rendering into the terminal). See billet.js and tty.js

[AThilenius]

Todo list:

• [ ] Create an in-order delivery wrapper for Socket.IO. I suspect this is causing a lot of issues with term on unstable connections.
• [ ] Remove the reverse proxy in LoopBack, use direct-forwarding.
  • Client: sends a Socket.IO message to billet-io with userId and accessToken in data. One of three states is possible in LoopBack:
  • Container is connected: Forward request via it's registered socket. Ordering will be done in Billet.
  • Container needs to be created (like before), using the userId and accessToken for authentication. Then drop down to the next state.
  • Container is in a 'pending boot' state, buffer messages until it's ready.
  • Messages from container to client fall into one of two states:
  • Client has an active connection, forward it on.
  • Client isn't connected, buffer the messages with a limit.
  • Container registers itself once it's booted, and that io Socket is used for communication.
• [ ] Clean up Angular code, it's a damn mess.
  • The billet.js service needs to be gutted and rethought.
  • The term.js directive needs to be reworked for the new billet.js service.