Well to start off, you'll need to choose your favorite server side language such as asp, jsp, php and so on and so forth.
All of these languages have the ability to produce a WAP site.
Next you'll need to set up the MIME types if they haven't already been done.
To enable support for WAP / WML pages on a UNIX based system,
add the following MIME Types through your Control panel or inside a .htaccess file:
.wmlc application/vnd.wap.wmlscript
.wmls text/vnd.wap.wmlscript
.wmlsc application/vnd.wap.wmlscriptc
.wbmp image/vnd.wap.wbmp
WAP support on a Windows system
You don't need to install a new WAP server to use this protocol. You can just WAP-enable IIS. To WAP-enable IIS, follow these steps:
Open the Microsoft Management Console (MMC), and right-click the computer name you want to WAP-enable.
Select Properties.
Under the Computer MIME Map heading in the Internet Information Server tab, click File Type.
Click New Type.
Enter wml in the Associated Extension box.
Enter text/vnd.wap.wml in the Content MIME box.
Repeat steps 1 through 6 for each of the file types
Associated Extension Content Type (MIME)
.wmlc application/vnd.wap.wmlscript
.wmls text/vnd.wap.wmlscript
.wmlsc application/vnd.wap.wmlscriptc
.wbmp image/vnd.wap.wbmp
After you've WAP-enabled IIS, you can add the functionality of Active Server Pages (ASP) to your .wml documents. At present, .wml documents are static. By adding the asp.dll to create a .wml document, you can create such functional elements as database access and dynamic pages. To create ASP-enabled .wml pages, add the following line to the top of your page (you must complete steps 1 through 7 before adding this code, which only works on .asp files):
<% response.ContentType = "text/vnd
.wap.wml" %>
This line forces the server to output a text-based .wml file that the WAP-enabled device can understand.
With the global move toward digital wireless technology, WAP is going to become an important specification in the future. WAP-enabling IIS is easy and fast, and the addition of ASP can result in eye-catching, dynamic information for your wireless technology users.
All of these languages have the ability to produce a WAP site.
Next you'll need to set up the MIME types if they haven't already been done.
To enable support for WAP / WML pages on a UNIX based system,
add the following MIME Types through your Control panel or inside a .htaccess file:
.wmlc application/vnd.wap.wmlscript
.wmls text/vnd.wap.wmlscript
.wmlsc application/vnd.wap.wmlscriptc
.wbmp image/vnd.wap.wbmp
WAP support on a Windows system
You don't need to install a new WAP server to use this protocol. You can just WAP-enable IIS. To WAP-enable IIS, follow these steps:
Open the Microsoft Management Console (MMC), and right-click the computer name you want to WAP-enable.
Select Properties.
Under the Computer MIME Map heading in the Internet Information Server tab, click File Type.
Click New Type.
Enter wml in the Associated Extension box.
Enter text/vnd.wap.wml in the Content MIME box.
Repeat steps 1 through 6 for each of the file types
Associated Extension Content Type (MIME)
.wmlc application/vnd.wap.wmlscript
.wmls text/vnd.wap.wmlscript
.wmlsc application/vnd.wap.wmlscriptc
.wbmp image/vnd.wap.wbmp
After you've WAP-enabled IIS, you can add the functionality of Active Server Pages (ASP) to your .wml documents. At present, .wml documents are static. By adding the asp.dll to create a .wml document, you can create such functional elements as database access and dynamic pages. To create ASP-enabled .wml pages, add the following line to the top of your page (you must complete steps 1 through 7 before adding this code, which only works on .asp files):
<% response.ContentType = "text/vnd
.wap.wml" %>
This line forces the server to output a text-based .wml file that the WAP-enabled device can understand.
With the global move toward digital wireless technology, WAP is going to become an important specification in the future. WAP-enabling IIS is easy and fast, and the addition of ASP can result in eye-catching, dynamic information for your wireless technology users.
Comment