chat ai final planning

[Jyustin]

planned features:

• [x] implement websocket connection within ai calls to:
• [x] implement chat history with seperate user SQL Data with JWT
• [x] establish real time connection between frontend and backend
• [x] add streaming ai text instead of instant text <-----------2nd feature (likely not possible with the time we have)------------------->
• [ ] implement a more useful version of chat history deletion:
• delete all of the chat history at once
• or delete individual messages

for websockets: use rachit's documentation to develop issue websocket backend repo

What i know: websockets can establish real time connection for chat interface if we build websockets onto our ai chat feature then any requests could be passed through websocket so we could add our realtime features.

we will need to make some heavy rewrites to our codebase though if the websockets cannot be contained to one method.

if websockets work like the image above then the serverside should be able to tell user if the chat is still generating, and also stream its output in realtime instead of instant sending of message.

process:

• [x] websocket implementation on backend by creating websocketconfig.java
• [x] use this class in chat.java and aichatbotcontroller.java so all the methods pass through websocket
• [x] something should go here I don't think this will be that easy.
• [x] build our methods

very unsure about this but hopefully rachit will pull through with the documentation.

for delete: use my preivous documentations of bringing back previous chat history to then delete the data in the stored tables. After that, for the deleting individual messages, I can focus on a single parameter such as the message, or time_stamp to only delete certain messages.

SCHEDULE:

• [x] add basic websocket implementation tuesday, wednesday
• [x] implement the websockets into ai by accessing websocket class thurdsay - friday next week:
• [x] test and deploy changes tuesday
• [x] improve delete functionality Wednesday (may not get to if the websocket development is too long)

for live review: plan to present first basic websocket demo but on our backend, currently websocket is on an entirely different backend but moving this to actual backend would be better for faster development

then show new ai feature, which will now 'stream' the response to user calls, and will display a thinking bubble while the API call is incomplete.

for N@TM: let people use the feature if they get stuck on a problem.

[Jyustin]

Progress report 5/28/24

websocket implementation has been difficult so features related to ai using websockets may not happen, on the other hand the streaming of ai text (justin) and delete functionality has been achieved.

Moving forward, the option is to either figure out websockets to add a feature or improve existing features.

feasible tasks

• [x] add ability of users to change between streamed response and immediate response
• [x] implement chat history with seperate user SQL Data with JWT
• [ ] improve upon deletion by allowing deletion of specific messages (could append button to message that calls delete method which deletes specific message)
• [ ] add updating specific messages (same procedure for deletion of messages)

on the table

• [ ] multiplayer chatting via websockets (not something other chat features have but is unlikely for the time being)