a very cool article on how facebook splits its page into “pages” in order to maximize the work performed by the server and browser when building a complex page that captures various resources (ads, channels, friends, etc.). they call it "big."
steve souders did talk about this in one of his conversations, and he called it an "early document."
in .NET, you cannot easily do this, but I did this by overriding the rendering method and flushing the response buffer earlier, so that is possible and it works very well. but I never tried it on this large scale. my question is, is it possible to build BigPipe in .NET? they said they built them in Java and PHP. I think this can be done in .NET as well, but I wonder if the winforms.NET architecture can be suboptimal for doing something like this.
I’m thinking about pushing a project for our company to create something similar - but you will need to do a lot more research, because it will not be a small project. I would like to build something that could help break any arbitrary page into these "pages". in .NET, it would be nice to include our user controls in these "brochures" and "wash" them all in pieces - BigPipe style.
comments / thoughts?
source
share