W3C home > Mailing lists > Public > public-bpwg@w3.org > July 2009

RE: MWABP: general / Yahoo guidelines

From: Jo Rabin <jrabin@mtld.mobi>
Date: Wed, 1 Jul 2009 11:19:17 +0100
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B401FF42A7@mtldsvr01.DotMobi.local>
To: "Eduardo Casais" <casays@yahoo.com>, <public-bpwg@w3.org>
Good idea to cross validate with other opinions out there. Ref
multipart, didn't we just discuss that and decide that there isn't
sufficient support?

I suppose also that taken in tandem with thoughts about caching, you'd
need to think about making sure that anything in a multipart document
had the same caching properties?

Jo

> -----Original Message-----
> From: public-bpwg-request@w3.org [mailto:public-bpwg-request@w3.org]
On
> Behalf Of Eduardo Casais
> Sent: 01 July 2009 10:35
> To: public-bpwg@w3.org
> Subject: MWABP: general / Yahoo guidelines
> 
> 
> The developers' site of Yahoo provides an interesting list
> of "Best Practices for Speeding Up Your Web Site":
> 
> http://developer.yahoo.com/performance/rules.html
> 
> Unsurprisingly, there is considerable overlap with what
> can be found in comparable guidelines from other firms,
> and with the MWABP as well. However, it is still
> instructive to look at their detailed justifications and at
> the rules that do not appear in the MWABP.
> 
> There are two interesting guidelines that are specifically
> for mobile devices only:
> 
> Keep Components under 25K (because, among other
> issues, the iPhone does not cache larger resources -- an
> issue I had already seen mentioned here and there; these
> 25K are as well quite compatible with usual BP for mobile
> devices).
> 
> Pack Components into a Multipart Document (with the
> caveat that one must check whether the device supports
> multiparts).
> 
> A quick cross-check might be in order, if it has not been
> done before.
> 
> 
> E.Casais
> 
> 
> 
Received on Wednesday, 1 July 2009 10:19:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:01 UTC