-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move away from Event subscription protocol #106
Comments
👍 |
Although REST D-Bus is useful. Here are a couple of reasons why OpenBMC has moved away from the REST D-Bus
More information can be found in: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/29344 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I still see the Event subscription protocol used here:
webui-vue/src/store/plugins/WebSocketPlugin.js
Line 25 in 780733a
See below for more information on the Event subscription protocol:
https://github.com/openbmc/docs/blob/224266ecfd528544e9f5473cc4607d9b6b7c435f/rest-api.md#event-subscription-protocol
The Event subscription protocol is behind the rest meson option in bmcweb which is defaulted off:
https://github.com/openbmc/bmcweb/blob/6f8273e49cffdd347c223b9538558edfb05e818a/meson_options.txt#L45
webui-vue should move away from these event subscription protocol websockets and to Server-Sent Events (SSE). openbmc/bmcweb@5e44e3d
I suspect this is the cause of #102. Overall we should move away from Event subscription protocol
The text was updated successfully, but these errors were encountered: