Use less definitive language for domain sharding

With the rise of mobile (and Google SPDY) it *might* no longer given that domain sharding is still best practice, even though it's still being discussed (mobile: http://www.mobify.com/blog/domain-sharding-bad-news-mobile-performance/) (pros and cons: http://www.stevesouders.com/blog/2013/09/05/domain-sharding-revisited/)
This commit is contained in:
Niklas B 2014-05-23 08:46:47 +02:00
parent e9474a8830
commit d5df1268dd
1 changed files with 4 additions and 1 deletions

View File

@ -52,8 +52,11 @@ The majority of the questions were plucked from an [oksoclap](http://oksoclap.co
* CDN Hosted
* Caching
* etc.
* Why is it better to serve site assets from multiple domains?
* Traditionally, why has it been better to serve site assets from multiple domains?
* How many resources will a browser download from a given domain at a time?
* What are the exceptions?
* Bonus points for identifying mobile as a possible downside (http://www.mobify.com/blog/domain-sharding-bad-news-mobile-performance/)
* Bonus points for identifying SDPY as an exception
* Name 3 ways to decrease page load. (perceived or actual load time)
* If you jumped on a project and they used tabs and you used spaces, what would you do?
* Suggest the project utilize something like EditorConfig (http://editorconfig.org)