Shashi Anand B wrote:
oops!! forgot to mention in the previous mail that the testing has to be done on the WAP side. The requirement is as follows : I need to generate a lot of WAP requests that go through the gateway to the web server and measure the average response time. Since, I have my application deployed in the gateway, these requests will go through the application and hence, I can measure its throughput.
ah, ok, this means you do not HTTP proxy the request to an extenal HTTP server (apache or others), you coded it into wapbox?
Interesting approach. Had something similar in mind some years ago in glue'ing Apache's core HTTP processing and Kannel's wapbox together to eliminate the HTTP communication layer, but never had time to pick from the NICE_TO_HAVE list.
In order to generate a huge "input stream" you obviously can use test/fakewap as a client?!
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
