Http request problem!

[rekha2103]

Hi all,
I have made a j2me application which works on a http network but the response i get from the server is slow.
And the user need to wait for few seconds before he gets a response and is re-directed to another page(form).
Do i need to add a gauge for letting the user wait till he is re-directed to other page..is it good to add gauge after every page(form)...how do i solve this problem?
is there any alternative available?

[vexed]

Adding gauges are good so the user doesnt think its a bum app that is just going to timeout. You could also build a flash loader for it also. But as far as one from every page. Not such a good idea. The app will seem laggy and not receive good ratings. May I suggest moving your webserver to a more centralized backbone? There are many free services that you can use that are in more centralized locations for mobile phones to access quicker.

[johnf1_coolguy]

Yes you can use a gauge on alert for each http request saying that some process in goin on and after some time throw a timeout for the connection,because user cant wait for so long. its better to give a timeout and to make the user feel comfort in retrying the request than to wait for the response!

[rekha2103]

thank you for the help..i'll surely add gauges

[im2amit]

Hi all,
I have made a j2me application which works on a http network but the response i get from the server is slow.
And the user need to wait for few seconds before he gets a response and is re-directed to another page(form).
Do i need to add a gauge for letting the user wait till he is re-directed to other page..is it good to add gauge after every page(form)...how do i solve this problem?
is there any alternative available?

Is all the forms or the pages of your application depends on the server response ? If yes.. then the app will useless in the scenarios of non availability of data network.
Which is the case for browser based, so for providing better user experience to the end users... try to add some offline capabilities to you app.

Server response is slow.... are you trying to generate the entire UI markup on the server side and then pushing it the client... try to minimize the data packets or the server response size for better User experience.

[rekha2103]

Hi,Amithabh
Yes,i need to ping the server for all my requests....for validation....to retrieve data and display to the user...
i have no choice on that.

[im2amit]

Hi,Amithabh
Yes,i need to ping the server for all my requests....for validation....to retrieve data and display to the user...
i have no choice on that.

I would still suggest to reduce the packet size of your server response, try to club few request together, move some validations to clientside if possible (/w static rules).
You can also try to keep a network socket connection open (to avoid handshake time for every network call) and reuse the same pipe to get more data or client/server interaction when needed.

[bhanuchandar.k]

Hi Amitabh,

I have few question :

reduce the packet size of your server response

What does this means ? Is it reducing the entire data size or Configuring the smaller MTU ?

Which one will be the better smaller MTU or bigger MTU for faster data transfer.

[im2amit]

I meant reduce the entire data size.

I should not have used term packet size here, bigger MTU will be faster.

Adding some type of catching infrastructure might also help.