If you are interested in state changes it is better to stick with server sent events (SSE). This is part of REST api which will keep long lasting connection to broadcast updates to connected clients.
This is the way in which UI is tracking things.
In case you need even higher performance there is an open PR in openhab-core to add support for websockets.
Thanks, but our intention is not keep a long lasting connection with Client (UI). it is just to know the current state and that is on demand. In that regards do you have any Idea, how many concurrent connections to REST api OpenHAB can handle ?
I am not aware of limitations and all my clients (smartphones, wallmountd tablets etc.) did ot report any issues so far. It all depends on the hardware running your openHAB instance and how fast it can answer the request.