Note: Support for WAP was discontinued in June 2011 When recording against a WAP Emulator (such as those provided by Nokia or OpenWave) you may get UDP functions recorded as opposed to WAP functions, e.g. WebUdpCreate(hUdp0);WebUdpSendTo(hUdp0, "192.168.01.01", 9200, "\h004015687474703A2F2F7761702E676F" // @http://wap.go 00000000 "\h6F676C652E636F6D81EA818481030203" // ogle.comj 00000010 "\hE88094809580A1809DA94E6F6B69612D" // h!)Nokia- 00000020 "\h5741502D546F6F6C6B69742F312E3200" // WAP-Toolkit/1.2 00000030 Instead of: WapUrl("http://wap.server.com", 0.80); Every WAP Emulator has the option to use either the WAP or HTTP protocol for communication with the server. To record a WAP Script in SilkPerformer it is necessary to configure the WAP emulator to use the HTTP protocol, not the WAP protocol. SilkPerformer does not record the WAP protocol; instead it records at HTTP level and then generates a WAP script. Old KB# 18274
↧