You're better of accessing the $HTTP_ACCEPT environment variable at the top
of your regular page and sending the WAP users to the WAP page. You can run
regular expressions on it to see if it contains "wml" or "hdml". At least
that's what I've done.

Data Driven Design
1506 Tuscaloosa Ave
Holly Hill, Florida 32117

http://www.datadrivendesign.com
Phone: (386) 226-8979

Websites That WORK For You
----- Original Message -----
From: "Davies, Elizabeth H." <EHDavies(at)West.com>
To: "HWG-technique Mailing List (E-mail)" <hwg-techniques(at)hwg.org>
Sent: Friday, August 10, 2001 11:33 AM
Subject: Wireless phone pages


> Has anyone here done a dual interface where you have a web page that is
> reachable by both regular browsers and also a phone? I am tasked at
building
> a cellular phone page that offers same/similar functionality of site. Big
> backend on this one. Is it possible to use the same middleware with two
> separate fronts? Lots of questions on this end, with no idea where to
start.
>
>  The WAP interfaces are one of the bells and whistles the PTB's wish
> researched for feasiblity and scalability.
>
> Elizabeth Davies
> Web Designer
> West Corporation
> (402)573-3386 or X206-7562
>
>

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA