On Thu, May 8, 2008 at 10:32 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I am actually of the opposite opinion regarding /mobile and > m.example.com. > I remember seeing sites use: m.example.com, wap.example.com, > mob.example.com, mobile.example.com > The result for me is that I hardly ever bother trying to guess which > one is used and thuss do not use the mobile verson of the site. IMHO > the site should automatically adapt to the smaller screen and less > capable browser. And for most normal websites contain the same content > (eg news, products, contact info...) formatted for smaller screens. Oh you misunderstood me :) i would also do the automatic checking - i just noticed some users do use m.example.com and in this way you *know* they want the mobile version. So by all means the automatic way is the way to go - just its good to assume that automatic doesnt work for everyone and it would be good to give people the alternative so they can force the mobile version.
Btw the browser check isn't so resource intensive :) its one regexp. -- Marcin Domanski http://kabturek.info --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
