Still Confused about WAP
#1
Still Confused about WAP
ok, i must be an idiot. i read through all the crap from all the forums and i still have questions.
i understand that the express network gives you access to the internet for your computer. i also understand that you can connect to the internet on your phone using this feature. i tried setting it up but i can't seem to connect. i have the following setup on my motorola t720 through verizon:
homepage: wap.oa.yahoo.com
wap ip: 207.232.99.109
wap port: 9201
can anyone tell me what i'm doing wrong. do i not understand it correctly? isn't this like mobile web where you can surf the net with your phone, check your hotmail, etc. or is wap something different? i don't need the laptop function right now, but the mobile web function would be great to occasionally check email on my phone.
any help would be much appreciated.
i understand that the express network gives you access to the internet for your computer. i also understand that you can connect to the internet on your phone using this feature. i tried setting it up but i can't seem to connect. i have the following setup on my motorola t720 through verizon:
homepage: wap.oa.yahoo.com
wap ip: 207.232.99.109
wap port: 9201
can anyone tell me what i'm doing wrong. do i not understand it correctly? isn't this like mobile web where you can surf the net with your phone, check your hotmail, etc. or is wap something different? i don't need the laptop function right now, but the mobile web function would be great to occasionally check email on my phone.
any help would be much appreciated.
#3
#4
Bringing one back...
I don't know why the settings would be needed unless required. Most services don't require settings to be in place. But that wap.oa.yahoo.com is valid for WAP/WML standards.
I just set up a web server which will be used for our sales people to get information from our database and did not need to set up the phone; just purchased the mMode service (AT&T).
As a side note I did find a good tool to test the mobile sites:
http://www.wapsilon.com/?q=1;t=n7210...//wapsilon.com
I don't know why the settings would be needed unless required. Most services don't require settings to be in place. But that wap.oa.yahoo.com is valid for WAP/WML standards.
I just set up a web server which will be used for our sales people to get information from our database and did not need to set up the phone; just purchased the mMode service (AT&T).
As a side note I did find a good tool to test the mobile sites:
http://www.wapsilon.com/?q=1;t=n7210...//wapsilon.com
#5
WAP - demistified....
WAP = Wireless Application Protocol.
What you need to understand is that there are two types of WAP browsers. The majority of them today support the "WAP" protocol which is WML formating. The newer handsets utilize WAP 2.x which support HTML formatting. Some do both, but most do one or the other (handset manufacturers put whichever the carrier wants, but not both, to save on memory).
For the WAP 1.x protocol, the handsets browser settings (defined by the carrier, and preset) consist of mainly the gateway IP address and port #, which resides on the carriers data network. By default, all WAP browsers have a homepage setting of www.openwave.com. The gateway can then redirect the page accessed to an internal WAP homepage with content the carrier has defined (sometimes through partnerships with third parties like MSN, Yahoo, etc). It is possible to direct your WAP browser to other WML sites, provided the carrier doesn't block it with firewalls or proxies, and the site is formatted correctly for the browser.
For WAP 2.x capable browsers/handsets, the same applies, however graphic and format rich content can be sent to the handset.
In either case, getting on the data network to access the carriers WAP content, or a page/site you shoose to see is dependant on thier data offerings. In some cases, you have to sign up for the "WAP" service. In Verizon's case, it's called mobile web.
WAP = Wireless Application Protocol.
What you need to understand is that there are two types of WAP browsers. The majority of them today support the "WAP" protocol which is WML formating. The newer handsets utilize WAP 2.x which support HTML formatting. Some do both, but most do one or the other (handset manufacturers put whichever the carrier wants, but not both, to save on memory).
For the WAP 1.x protocol, the handsets browser settings (defined by the carrier, and preset) consist of mainly the gateway IP address and port #, which resides on the carriers data network. By default, all WAP browsers have a homepage setting of www.openwave.com. The gateway can then redirect the page accessed to an internal WAP homepage with content the carrier has defined (sometimes through partnerships with third parties like MSN, Yahoo, etc). It is possible to direct your WAP browser to other WML sites, provided the carrier doesn't block it with firewalls or proxies, and the site is formatted correctly for the browser.
For WAP 2.x capable browsers/handsets, the same applies, however graphic and format rich content can be sent to the handset.
In either case, getting on the data network to access the carriers WAP content, or a page/site you shoose to see is dependant on thier data offerings. In some cases, you have to sign up for the "WAP" service. In Verizon's case, it's called mobile web.
#6
So which browsers (services and devices) are currently supporting 2.0?? Some of the reading I have found stated that 2.0 hasn't been really used yet. 1.2 has minimal use with most browsers supporting 1.1.
The reason I ask is because of the deployment I am starting. This is not my field and we are a small company so I don't have a staff to do this stuff. I would like to get the most out of it the first time (as would anyone but we are very resource limited).
It seems that I might be safer sticking with the 1.1 standard for now and then migrating and adding functionality as 2.0 is more widely adopted. But if everyone is now supporting 2.0 I might as well add the additional functionality gained with the newer standard.
Oh yea:
The reason I ask is because of the deployment I am starting. This is not my field and we are a small company so I don't have a staff to do this stuff. I would like to get the most out of it the first time (as would anyone but we are very resource limited).
It seems that I might be safer sticking with the 1.1 standard for now and then migrating and adding functionality as 2.0 is more widely adopted. But if everyone is now supporting 2.0 I might as well add the additional functionality gained with the newer standard.
Oh yea:
Trending Topics
#9
Originally Posted by scalbert
Oh yea, and I am testing with my Motorola V600 using AT&T mMode. I assume this can support WAP 2.0. I know it works fine with 1.1 from the initial testing I have done.
#11
Originally Posted by suXor
Yeah, the V600 has WAP 2.0
I definitely need to find some good reading material on 1.1 and 2.0, know of any good books??
Thread
Thread Starter
Forum
Replies
Last Post
Greengecko
3G TL Audio, Bluetooth, Electronics & Navigation
4
09-16-2015 09:19 PM