Using web sockets to update clients

[georgweiss]

I'd like to propose employing a web socket-based approach for two particular use cases:

1. Olog client where currently a background thread is polling for new log entries. Using web sockets the service may instead notify clients when a new log entry is created (or updated).
2. Save-and-restore data is currently not refreshed in the client unless user collapses and then expands a node in the tree view. I have a user requirement to implement a refresh button, but pushing updates from service through web sockets would in my view be the preferable approach.

That said, web sockets on server side is quite straight forward as it is well supported in Spring Boot. On the client side however, the Java native APIs are a bit crude and not very developer friendly. Relying on (for instance) Kafka to do a similar job seems a bit overkill and would add another service dependency for both Olog and save-and-restore.

My question/idea:

1. Any reasons to not use web sockets?
2. Any reasons to not employ a 3rd party web socket client lib (e.g. a Spring lib)?