Add WebSocket endpoint for chatbot and Todo.description #42
Conversation
|
@phillip-kruger ^ for the TODO UI |
|
@cescoffier is that what you had in mind for the WebSocket? |
The reason I created the Thinking out loud, I could use just |
|
My advice when using web socket: See them as TCP connection. So on top of that you need to design and implement a protocol (that's why we often use json rpc on top of web socket in Quarkus as it provides a framing protocol). In your case I would create a few message type, with a 'kind' attribute to distinguish them. |
Will use WebSocket for bidirectional message to and from server Added a description for Todo for the new UI
emmanuelbernard
force-pushed
the
todo-agent
branch
from
ba2f93a to
4e661b6
Compare
Applied your changes @rsvoboda, thanks ! |
Signed-off-by: Phillip Kruger <[email protected]>
Screencast_20250930_194415.mp4 |
To test, go to UI, click on a TODO then click on Create with AI green button Then look at stack trace
This simplifies the subscription barrier issues
Use CDI async event to pass info to AgentDispatcher Create a Context holder for per todoId request after move to @ApplicationScope
Rename to AgentsMediator (from dispatcher)
Signed-off-by: Phillip Kruger <[email protected]>
Screencast_20251003_165042.mp4 |
Also adapt to different TAsk event behaviors And ad more activity logs
Will use WebSocket for bidirectional message to and from server
Added a description for Todo for the new UI
Here it is Phillip, I created an new field description for Todo
And created a WebSocket endpoint as /todo-agent/{todoId}