WAP/WML Programming for App. Servers

More documents

Recommendations

Info

WAP challenges: diverse platformsIdeal: all WAP gateways/devices fully implement the same versionof the standard Reality: varying levels of support for different featuresSecond best: all the users of my app are running the same deviceusing the same gateway Reality: even within the same organization you will find differentdevicesReality: either Write to lowest common denominator (weak) Make applications adapt to devices (need framework)Conference Call: 888-311-9053International 908-228-9011
Identifying the target platformUse User-Agent field of the incoming request Call getHeader("User-Agent") on HttpServletRequest Some sample User Agents: Nokia7110/1.0(04.84) MOT-D5/4.1.5 UP/4.1.16f Slurp.so/1.0 (slurp@inktomi.com;) See http://internetalchemy.org/wap/ualist.phtmlNot all browsers or gateways send a User-Agent If a site supports both HTML and WML Run the WML site on virtual host wap.***.comto distinguish it from Web requests on www.***.comConference Call: 888-311-9053International 908-228-9011
Page 1 and 2: WAP/WML Programming for App. Server
Page 3 and 4: Who is the target audience?Develope
Page 5 and 6: WAP/WMLfor J2EE developersConferenc
Page 7 and 8: WML overviewWelcome to SilverStream
Page 9 and 10: J2EE Patternsfor WAP/WMLConference
Page 11: Back-end connectivity on the server
Page 15 and 16: XML/XSLT using JSP Custom tags (1)A
Page 17 and 18: Keeping state for WAP applicationsW
Page 19 and 20: WAP/WML Applicationsin a larger con
Page 21 and 22: PersonalizationPersonalization is K
Page 23 and 24: J2EE provides a solid framework for
Page 25: Inside J2EE Online Seminars - NextN

WAP/WML Programming for App. Servers

Create successful ePaper yourself

Delete template?

Save as template?