> -----Original Message----- > From: cyberarian [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 8:43 AM > To: users@httpd.apache.org > Subject: Re: [EMAIL PROTECTED] first email to this list > > Thanks for prompt response. My HTML files are running quite > fine in my browser by visiting http://localhost > what to do next?
You just put a WAP file (ie, page.wml) in the server (eg, http://server/page.wml) then hit that URL from the phone. I get the feeling you're not really sure about how WAP works... It's really just the same as normal HTTP - the only difference is that the content is in a different mark-up language (eg, WML or HDML instead of HTML). The other big difference is that the phone doesn't connect directly to the server, rather, it sends a request to an HTTP gateway computer in the base station and it is the gateway that makes the request (via the internet) to the server. So the phone -> gateway link is over GPRS/UTMS/EDGE or whatever and the gateway -> server link is over Plain Old HTTP. If all you've got is an apache server on localhost then it obviosuly won't work - your server needs to be accessible on the public internet, with a registered domain name and public IP and everything. Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > > cyberarian > > > On 1/24/07, Boyle Owen <[EMAIL PROTECTED]> wrote: > > > -----Original Message----- > > From: cyberarian [mailto:[EMAIL PROTECTED] ] > > Sent: Wednesday, January 24, 2007 7:33 AM > > To: users@httpd.apache.org > > Subject: [EMAIL PROTECTED] first email to this list > > > > Hi all i m the new user of this list. can someone guide me > > how to use apache webserver for wap files. I have an > > index.wap file. How can i use it from my mobile using my > > apache web server? > > > > The WAP file goes on the apache server. The mobile > phone is the client - > it fetches the file from the server and renders (ie, > displays) it. > > Forget about WAP for the minute - get apache running > with a plain HTML > file that you can see in a browser then start worrying > about WAP. > > Rgds, > Owen Boyle > Disclaimer: Any disclaimer attached to this message may > be ignored. > > > This message is for the named person's use only. It may > contain confidential, proprietary or legally privileged > information. No confidentiality or privilege is waived or > lost by any mistransmission. If you receive this message in > error, please notify the sender urgently and then immediately > delete the message and any copies of it from your system. > Please also immediately destroy any hardcopies of the > message. You must not, directly or indirectly, use, disclose, > distribute, print, or copy any part of this message if you > are not the intended recipient. The sender's company reserves > the right to monitor all e-mail communications through their > networks. Any views expressed in this message are those of > the individual sender, except where the message states > otherwise and the sender is authorised to state them to be > the views of the sender's company. > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache > HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html > for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
