Hi Max,
On Mar 29, 2013, at 10:45 AM, Max Semenik maxsem.w...@gmail.com wrote:
Hi, we at the mobile team are currently working on improving our
current hit rate, publishing the half-implemented plan here for review:
== Proposed strategy ==
* We don't vary pages on X-Device anymore.
*
On 02.04.2013, 20:16 Mark wrote:
I've been pondering a bit about the two options for serving mobile
ResourceLoader requests with Varnish: on the bits caches or on the
mobile caches. I don't fully like either option to be honest. On one
hand I'd like to keep mobile device detection off our
On 30.03.2013, 2:40 Asher wrote:
Why don't we continue to use the bits cache for all things
resourceloader. Can you provide a different path for these requests, such as
instead of:
http://bits.wikimedia.org/en.wikipedia.org/load.php?..
use something like:
Hi, we at the mobile team are currently working on improving our
current hit rate, publishing the half-implemented plan here for review:
== Current status ==
* X-Device header is generated by frontend Varnish from user-agent.
* There are currently 21 possible X-Device values, which we decreased
This sounds like a great plan. Thank you!
On Fri, Mar 29, 2013 at 2:45 AM, Max Semenik maxsem.w...@gmail.com wrote:
Hi, we at the mobile team are currently working on improving our
current hit rate, publishing the half-implemented plan here for review:
== Current status ==
* X-Device
Max, do we still plan to detect javascript support for mobile devices, or
do you want to fold that into isWAP ?
Non-js-supporting devices need very different handling, as all HTML has to
be pre-built for them on the server.
On Fri, Mar 29, 2013 at 2:45 AM, Max Semenik maxsem.w...@gmail.com
On 29.03.2013, 21:47 Yuri wrote:
Max, do we still plan to detect javascript support for mobile devices, or
do you want to fold that into isWAP ?
Non-js-supporting devices need very different handling, as all HTML has to
be pre-built for them on the server.
ResourceLoader has a small stub
This approach will require either:
1) Adding device detection to bits for device variance
2) Using mobile varnish to handle load.php requests for resources requested
from .m domains
From conversations with Max and some folks from ops, it sounds like #2 is
the preferred approach, but I am a
Why don't we continue to use the bits cache for all things resourceloader.
Can you provide a different path for these requests, such as instead of:
http://bits.wikimedia.org/en.wikipedia.org/load.php?..
use something like:
http://bits.wikimedia.org/m/en.wikipedia.org/load.php?..
Then we can if
