in some cases it would be better, if the backend would push messages to the frontend instead of the frontend regularly polling (for example for retrieving the number of free bikespots).
however i think in this case anyone could listen to the messages. for the bikenest service its okay, but if we want to publish messages that should only be received by one user, we should probably do it different.
in some cases it would be better, if the backend would push messages to the frontend instead of the frontend regularly polling (for example for retrieving the number of free bikespots).
i think this usecase might not be so hard, i found a tutorial for spring here: https://spring.io/guides/gs/messaging-stomp-websocket/
however i think in this case anyone could listen to the messages. for the bikenest service its okay, but if we want to publish messages that should only be received by one user, we should probably do it different.