Bi-directional communication between client and operator.
Lost the ability to send messages via API due to needing to refactor how socket connections are saved on the daemon. Before, we would save the socket connection on the client or operator objects, this poses some problems with reuse, as well as includes an unnecessary socket key on API response. For now I'll leave out the ability to post messages via API to a client (from an operator) with a 405 or 501.
Refactored how Client, Operator and Chat's are created
Refactored Client, Operator, and Chat structs
Now only saving sockets in a key (socket ID) / value (actual socket) array on the socket server object
Added chat:new message and emits it to both operators and client that joined (to pass back the socket ID)
Bi-directional communication between client and operator.
Lost the ability to send messages via API due to needing to refactor how socket connections are saved on the daemon. Before, we would save the socket connection on the client or operator objects, this poses some problems with reuse, as well as includes an unnecessary socket key on API response. For now I'll leave out the ability to post messages via API to a client (from an operator) with a 405 or 501.
chat:newmessage and emits it to both operators and client that joined (to pass back the socket ID)operator:messagefunctionality