aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Lange <code@nerdmind.de>2016-06-26 16:38:20 +0200
committerThomas Lange <code@nerdmind.de>2016-06-26 16:38:20 +0200
commit28f2ba2a44ca932e16ba6791a07ed42b62fe6803 (patch)
tree4018079243daa49b2c41cd4219ae4a673ec2dcf8
parent21824df56bd13d81f10ac0b86c5cad31def51f3e (diff)
downloadbigpipe-28f2ba2a44ca932e16ba6791a07ed42b62fe6803.tar.gz
bigpipe-28f2ba2a44ca932e16ba6791a07ed42b62fe6803.tar.xz
bigpipe-28f2ba2a44ca932e16ba6791a07ed42b62fe6803.zip
Link changed to code.facebook.com
-rw-r--r--readme.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/readme.md b/readme.md
index 8a861d7..e744f40 100644
--- a/readme.md
+++ b/readme.md
@@ -2,4 +2,4 @@
> BigPipe is a fundamental redesign of the dynamic web page serving system. The general idea is to decompose web pages into small chunks called pagelets, and pipeline them through several execution stages inside web servers and browsers. This is similar to the pipelining performed by most modern microprocessors: multiple instructions are pipelined through different execution units of the processor to achieve the best performance. Although BigPipe is a fundamental redesign of the existing web serving process, it does not require changing existing web browsers or servers; it is implemented entirely in PHP and JavaScript.
**More information from *Changhao Jiang* at Facebook Engineering:**
-<https://www.facebook.com/notes/facebook-engineering/bigpipe-pipelining-web-pages-for-high-performance/389414033919> \ No newline at end of file
+<https://code.facebook.com/posts/162127837314007/bigpipe-pipelining-web-pages-for-high-performance/> \ No newline at end of file