So just to clarify this is for serving content and unrelated to Server-Sent Events (SSE)? I thought that HTTP/2 would be able to kill off WebSockets for such use cases.
Yes, HTTP/2 push was never related/similar to the use-case of SSE or WebSockets. In fact, WebSockets are currently being updated to allow them to work inside HTTP/2 frames (which is currently not possible)
It targets apispec v2 which I believe it’s still more common than v3. But that would still be called OpenAPI though. I didn’t put much thought on the name, “swagger” is just catchier than “OpenAPI”, it got more swag maybe? :D
I do include swagger ui, so the name is still somehow accurate as it also includes tools, and not just the apispec.
So just to clarify this is for serving content and unrelated to Server-Sent Events (SSE)? I thought that HTTP/2 would be able to kill off WebSockets for such use cases.
Yes, HTTP/2 push was never related/similar to the use-case of SSE or WebSockets. In fact, WebSockets are currently being updated to allow them to work inside HTTP/2 frames (which is currently not possible)
Thanks for helping me understand!
Isn’t it called OpenAPI for a few years now? Or does this target a much older version of the specification?
It targets apispec v2 which I believe it’s still more common than v3. But that would still be called OpenAPI though. I didn’t put much thought on the name, “swagger” is just catchier than “OpenAPI”, it got more swag maybe? :D
I do include swagger ui, so the name is still somehow accurate as it also includes tools, and not just the apispec.