On Mon, Jun 10, 2013 at 5:37 PM, Reza <[email protected]> wrote:
> Interesting, I wonder what the performance of this is (this is the > advanced mode): > > https://github.com/serbanghita/Mobile-Detect/blob/master/Mobile_Detect.php > Pretty sure that an order of magnitude slower than any Varnish based solution you can use to do your device classification. Examples of which are mentioned here: https://github.com/varnish/varnish-devicedetect/ The accuracy of the solution is intriguing. I guess that all of these solution can anyway be considered "part of the RESS (Responsive Web Design with Server-Side Component) movement" as Mobile-Detect describes itself. > How do devs keep these 'detectors' upto date? > Subscribe to the GitHub RSS feed and update the script everytime it gets updated? :-) > As for Varnish (or any caching layer or CDN), you just need to manually > add your mobile detection string to the hash or Vary on the User-Agent. > Certainly. And you can even move the classification (or was it detection) logic to the cache layer, which will be faster and likely more precise, at least using dClass and Apache DeviceMap ;-) From: Matt Korostoff <[email protected]> > To: [email protected] > Sent: Monday, June 10, 2013 11:25 AM > Subject: Re: Drupal Mobilizer > > > Drupal Developer here! I've been lurking on this list for a long time, but > this is finally a question I can field. > > Mobilizer has two modes "Standard" and "Advanced". Standard is based > *entirely > *on regex matching the UA string, which is available to us from the > superglobal $_SERVER variable. Here's the relevant portion of mobilizer > code where the binary "is mobile?" decision gets made: > https://gist.github.com/MKorostoff/5749419. Basically, the "is mobile?" > condition returns "true" if any of the "if" conditions succeed and the last > condition *does not* succeed. In "Advanced" mode, this logic > is superseded by the "Mobile Detect" php library > https://github.com/serbanghita/Mobile-Detect. > > Note the major drawback of this approach from a Drupal perspective is that > it would probably not work behind the the popular Varnish Cache reverse > proxy, which is now a standard part of essentially every enterprise Drupal > build (though there's likely Varnish configuration strategies to avoid > this). > > Best, > Matt > > On Mon, Jun 10, 2013 at 10:17 AM, Werner Keil <[email protected]> > wrote: > > > Hi, > > > > I wonder, how this Drupal extension for Mobile Web Apps accomplishes that > > > > - Your new mobile website will support any mobile device such as > iPhone, > > Android, Blackberry, and Symbian on any browser and any screen > > resolution. > > > > https://drupal.org/project/mobilizer > > > > Where anyone is looking into PHP clients for DeviceMap, having a look at > > some of the major CMS projects like Drupal or Typo3 probably can't hurt, > or > > trying to make a PHP tool usable by those, too. > > > > Werner > > > > * Eclipse DemoCamps Kepler 2013: June 19-28 2013, Germany, Denmark, > > Austria. > > Werner Keil, UOMo Lead, Mærsk DevOps Build Manager will present > > "Triple-E’class > > DevOps with Hudson, Maven, Kokki, Multiconf & PyDev", "M4M 2 the Rescue > of > > M2M" > > > Best regards, -- <http://www.varnish-software.com/>*Rubén Romero* Varnish Software AS Cell: +47 95964088 / Office: +47 21989260 Skype & Twitter: ruben_varnish We Make Websites Fly!Winner of the 2013 Red Herring Top 100 Europe Awards
