Ok, I see what you're asking. If tomorrow FB decided to become Shared App Web, then this would mean that they would no longer have to worry about how many redundant requests each user would make (just assuming there is no optimization whatsoever).
For example, if a user visits a page A, that page creates a WebSocket connection, and a new window opens with page A still creating a new WebSocket connection. Obviously, as the number of window pages increases, it will use more server resources. But this paradigm will only have one WebSocket connection, no matter how many browser windows there are.
That's the problem.
How much less server size can this paradigm use? It depends on how many windows all users are used to, and whether there are any optimizations made to support multiple browser windows. If an application doesn't have any multiple browser window optimization, then such a model can at least significantly reduce server usage (I would guess maybe 10%-50%)
Ok, I see what you're asking. If tomorrow FB decided to become Shared App Web, then this would mean that they would no longer have to worry about how many redundant requests each user would make (just assuming there is no optimization whatsoever).
For example, if a user visits a page A, that page creates a WebSocket connection, and a new window opens with page A still creating a new WebSocket connection. Obviously, as the number of window pages increases, it will use more server resources. But this paradigm will only have one WebSocket connection, no matter how many browser windows there are.
That's the problem.
How much less server size can this paradigm use? It depends on how many windows all users are used to, and whether there are any optimizations made to support multiple browser windows. If an application doesn't have any multiple browser window optimization, then such a model can at least significantly reduce server usage (I would guess maybe 10%-50%)
Thank you, that's really neat.