> Hi Pierre, Hi Willy, > The close on the server side is expected, that's a limitation of the current > design that we're addressing for 1.9 and which is much harder than initially >expected. The reason is that streams are independent in H2 while in H1 the > same stream remains idle and recycled for a new request, allowing us to keep > the server-side connection alive. Thus in H2 we can't benefit from the > keep-alive mechanisms we have in H1. But we're currently working on > addressing this. As a side effect, it should end up considerably simplifying > the H1 code as well, but for now it's a nightmare, too many changes at once...
OK, I conclude this SSE pattern is not working out-of-the-box when using h2 as of now. Is it still true even if setting the user set the proper connection headers on server side? Thanks, Pierre
