Its as simple as:
1. Sending the least amount of items down the tube 2. Use asset hosts to make the tube wider. Be aware that additional asset hosts == more dns lookups. Although, really; this is only an issue for the first http request to said host. On Wed, Apr 14, 2010 at 10:16 AM, Daniel Sabados <[email protected]>wrote: > Hi, > > > YSlow and Page Speed rant on about reducing DNS lookups by using a CDN, > whilst rails advocates multiple asset servers so that "browsers will open > eight simultaneous connections rather than two". > > Is one method of asset delivery clearly better than the other or does it > come down to best fit? > > > It'd be great to hear some opinions. > > > Thanks, > > > Dan. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
