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 little nervous about it since mobile varnish caches will have to handle a significant increase in requests. It looks like a typical article load results in 6 load.php requests. Also, we'll need to duplicate some configuration from the bits VCL. Ops, is this OK given current architecture? On Fri, Mar 29, 2013 at 11:18 AM, Max Semenik <[email protected]> wrote: > 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 module called startup. It checks > browser compatibility and then loads jQuery and various MediaWiki > modules (including ResourceLoader core). We just need to imporove the > checks, as the my original message states: > > > * Since now we will be serving ResourceLoader to all devices, we will > > blacklist all the incompatible devices in the startup module to prevent > > them from choking on the loads of JS they can't handle (and even if they > > degrade gracefully, still no need to force them to download tens of > > kilobytes needlessly)[3] > > -- > Best regards, > Max Semenik ([[User:MaxSem]]) > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
