As an end user of ui-shell-reader based on websocket server I want the server to not evict my reader. Currently it treats it like any other client and if inactivity is exceeded the reader is disconnected. Currently the reader does not produce any activity because it simply reports events generated by the server. Either the server should distinguish between reader and writer and not evict the reader or the reader should send heartbeats to the server to simulate activity.
As an end user of ui-shell-reader based on websocket server I want the server to not evict my reader. Currently it treats it like any other client and if inactivity is exceeded the reader is disconnected. Currently the reader does not produce any activity because it simply reports events generated by the server. Either the server should distinguish between reader and writer and not evict the reader or the reader should send heartbeats to the server to simulate activity.