jbleyel
jbleyel
Hi @wedebe , i see no real benefit in performance or traffic if we use websockets for single requests. Websockets will be a good solution if you have triggered changes...
Let me try a test version.
https://github.com/E2OpenPlugins/e2openplugin-OpenWebif/tree/websocket NOT TESTET!!!
We need autobahn on the feed and this works only on python3! So we should exclude this on python2. I will check this.
yes why, not the classic UI has also a higher timeout for the status info But the websockets implementation takes a while.
autobahn is on the feed soon
This is a special module to create/validate the schema and can be done differently. https://alecthomas.github.io/voluptuous/docs/_build/html/voluptuous.html# ``` REQUEST_BASE_SCHEMA = vol.Schema({ vol.Required('id'): int, }) BASE_MESSAGE_SCHEMA = REQUEST_BASE_SCHEMA.extend({ vol.Required('type'): vol.Any( TYPE_AUTH, TYPE_PING )...
Here are some examples. https://python.plainenglish.io/identify-websocket-clients-with-autobahn-twisted-and-python-3f90b4c135d4 https://www.programcreek.com/python/example/92376/autobahn.twisted.websocket.WebSocketServerProtocol https://www.fullstackpython.com/websockets.html
BUT.. as i said. The real benefit for websockets are push notifications. The push trigger source must be enigma. Enigma2 triggers the a function in OWF if something new data...
https://stackoverflow.com/questions/28613399/websocket-vs-rest-api-for-real-time-data/28618369#28618369