|
Posted by howa on September 4, 2007, 1:16 pm
Please log in for more thread options
Hello,
Any best practice in checking mobile device and re-direct them into
mobile page (e.g. wap) ?
E.g. User agent, screen size etc.?
anything else?
|
|
Posted by André Gillibert on September 4, 2007, 1:58 pm
Please log in for more thread options
howa wrote:
> Any best practice in checking mobile device and re-direct them into
> mobile page (e.g. wap) ?
>
I'm not a specialist, but the HTTP Accept: header seems to be the best
place to see what formats the user-agent likes.
It's even pounded with a quality ratio.
Apache's algorithm is a good example of clever content negotiation:
http://httpd.apache.org/docs/2.2/content-negotiation.html.en#methods
> E.g. User agent, screen size etc.?
No.
--
|
|
Posted by Rik Wasmus on September 4, 2007, 7:50 pm
Please log in for more thread options
> Hello,
>
> Any best practice in checking mobile device and re-direct them into
> mobile page (e.g. wap) ?
>
> E.g. User agent, screen size etc.?
>
> anything else?
Keeping the same data/html, possibly with another stylesheet (check the
media attribute). Wasn't WAP dead BTW? The only people I know who can
browse the internet on their phone just have a 'regular browser'.
--
Rik Wasmus
|
|
Posted by howa on September 4, 2007, 10:19 pm
Please log in for more thread options
Rik Wasmus
> Keeping the same data/html, possibly with another stylesheet (check the
> media attribute). Wasn't WAP dead BTW?
XHTML Mobile Profile is nice and easy to convert from current XHTML
|
|
Posted by David E. Ross on September 4, 2007, 8:09 pm
Please log in for more thread options
On 9/4/2007 10:16 AM, howa wrote:
> Hello,
>
> Any best practice in checking mobile device and re-direct them into
> mobile page (e.g. wap) ?
>
> E.g. User agent, screen size etc.?
>
> anything else?
>
If you plan to "sniff" for user agent, be very careful that you are
checking it correctly.
There are far too many Web sites that do sniffing to distinguish IE from
Firefox from Opera from Safari from etc. Often, there is no really good
reason for this other than the fact that some non-standard IE capability
has been used that won't work with other browsers.
In the meantime, sniffing for Firefox should actually be for Gecko
(Mozilla's Web rendering engine within Firefox). When Web sites sniff
specifically for Firefox and not Gecko, those sites often do not display
correctly for SeaMonkey, Camino, and other Mozilla products, all of
which are also using Gecko as does Netscape and more than 20 other
browsers. If Firefox can properly display a Web page, so should any
other Gecko brower PROVIDING there is poorly implemented sniffing. See
<http://geckoisgecko.org/> for a discussion on Gecko sniffing.
While my rant does not seem to apply to mobile devices, the Minimo
browser for mobile devices uses Gecko. Thus, my original warning: Be
very careful!
--
David E. Ross
<http://www.rossde.com/>.
Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation. © 1997
|
| Similar Threads | Posted | | Mobile devices | February 15, 2005, 10:33 am |
| Misunderstandings of Mobile HTML | March 29, 2005, 5:06 pm |
| How _not_ to do mobile pages | December 12, 2006, 7:44 am |
| newbie mobile web authoring questions | December 11, 2006, 11:11 am |
| Sound with Opera 8.60 for Windows Mobile | February 22, 2007, 1:16 am |
| Looking for solution for iPhone/Mobile Safari | June 19, 2008, 9:44 pm |
| Are there forum/group for discussing XHTML Mobile Profile? | January 14, 2008, 10:59 am |
| when nokia mobile browser at the first time access HTTP Server | May 8, 2005, 8:38 am |
| uMG ***Hot stuff - check this out !!! uMG | January 28, 2006, 12:37 pm |
| "opensearch.xml" check please | August 30, 2006, 3:03 pm |
|
XML Sitemap