Re: Server push - use cases

HTTP Server Push has been debated much in the API community, although widespread adoption has yet to materialise. I presented some of the use-cases at the 2019 HTTP Workshop, which can be viewed here:

https://asbjornu.github.io/prefer-push-presentation/

Kévin Dunglas has been a pioneer in the space, with his implementation of Server Push called “Vulcain":

https://github.com/dunglas/vulcain

I would love to see more, not less, adoption of Server Push going forward. The web isn’t browser-only; if it was, the HTTP specification would have dropped  support for other methods than GET + POST long ago (as an example). Thankfully, it hasn’t, and I think Server Push deserves a similar treatment.

(CC to the HTTP API WG)

--
Asbjørn Ulsberg    -=|=-    asbjorn@ulsberg.no
«He's a loathsome offensive brute, yet I can't look away»
On 14 Aug 2023, 11:01 +0200, Mark Thomas <markt@apache.org>, wrote:
> Hi all,
>
> I'm currently working on a update to the Jakarta Servlet specification
> and we are discussing whether or not to deprecate, and in a future
> version remove, support for server push.
>
> My impression from scanning this list's archives is that server push has
> not been widely adopted. I am aware that browsers have dropped / are
> dropping support for server push.
>
> Can anyone point me to a current (or even proposed) use of server push
> that might be a reason not to deprecate server push in the Select spec?
>
> Thanks,
>
> Mark
>