WAP: Difference between revisions
No edit summary |
(XHTML has supplanted it) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
'''WAP''' or Wireless Application Protocol is part of the [[IMT-2000]] [ITU]] standards that includes [[GPRS]], [[Bluetooth]], [[DECT]] and [[UMTS]]. It has been the subject of much [[pro-technology propaganda]]. | '''WAP''' or Wireless Application Protocol is part of the [[IMT-2000]] [[ITU]] standards that includes [[GPRS]], [[Bluetooth]], [[DECT]] and [[UMTS]]. It has been the subject of much [[pro-technology propaganda]]. | ||
A maximum of 1397 bytes of compressed content per page is the maximum in order to work with currently fielded devices like a five-year-old, | |||
four-line-display [[Nokia]]. | |||
However, WAP is basically dead: [[XHTML]] and [[CSS]] have supplanted it, offering easier (and more widespread) implementation with very little additional overhead. | |||
"[[MediaWiki XHTML]] source is hardly ideal, but it works. The lightweight | |||
skins make it perfectly suitable for the kind of dynamic interaction we | |||
would ask from it with WAP, and for a more tailored interface there's | |||
always [[TomeRaider]]." - [http://mail.wikimedia.org/pipermail/wikipedia-l/2004-July/016048.html] | |||
=== references === | === references === | ||
*[http://www.gsm-technology.com/gsm.php/en,unlock,subpage_id,technologie_WAP.html WAP specs] | *[http://www.gsm-technology.com/gsm.php/en,unlock,subpage_id,technologie_WAP.html WAP specs] | ||
Latest revision as of 21:48, 18 July 2004
WAP or Wireless Application Protocol is part of the IMT-2000 ITU standards that includes GPRS, Bluetooth, DECT and UMTS. It has been the subject of much pro-technology propaganda.
A maximum of 1397 bytes of compressed content per page is the maximum in order to work with currently fielded devices like a five-year-old, four-line-display Nokia.
However, WAP is basically dead: XHTML and CSS have supplanted it, offering easier (and more widespread) implementation with very little additional overhead.
"MediaWiki XHTML source is hardly ideal, but it works. The lightweight skins make it perfectly suitable for the kind of dynamic interaction we would ask from it with WAP, and for a more tailored interface there's always TomeRaider." - [1]