I've implemented chat view.
A (signed-in) user can POST chat messages to the server at /chatbot/chat/ with text given as payload.
When the server receives messages, it forks a new process. The parent process saves the message in db while child process communicates with chatscript and creates appropriate response message.
GET request returns all the messages in which the user is involved.
Of course, un-authenticated users and other users cannot access the user's chatlog.
I've implemented chat view. A (signed-in) user can
POSTchat messages to the server at/chatbot/chat/withtextgiven as payload. When the server receives messages, it forks a new process. The parent process saves the message in db while child process communicates with chatscript and creates appropriate response message.GETrequest returns all the messages in which the user is involved.Of course, un-authenticated users and other users cannot access the user's chatlog.