NozFx

Hi all,

I have a weird problem with making HTTP calls across a newly created GPRS connection. Initially I thought a timeout was occuring during the connection process but after further testing I discovered that once the app fails it continues to do so even if the GPRS connection is alive and working. I have to restart my app to get it working. The strange thing is it is inconsistant. Sometimes it happens and sometimes not. The only pattern that exists is that it only happens when the app first starts and creates the GPRS connection.

This app is written in C# .NETCF2.0. I am running it on a HP Ipaq hw6915 with Windows Mobile 5. Is this a specific problem with code or hardware Do I need to be doing some form of RASDial before I begin to make my HTTP connections What would be the best way to track this

TIA

NozFx



Re: Smart Devices General HTTP Connection does not always work with GPRS connection.

PatickG

NozFx wrote:

The only pattern that exists is that it only happens when the app first starts and creates the GPRS connection.

Does it create the connection entry or does it establish the connection

Did you try to use IE with that connection when your app fails





Re: Smart Devices General HTTP Connection does not always work with GPRS connection.

NozFx

Hi Patick,

Sorry for the delayed repsonse, been on an extended away. Also, thank you for your reply.

Once my app repeatedly fails to connect I go to IE and I am able to establish a connection. Problem is my app does not seem to piggy back this new connection. I'm due to do some more field testing next week. There have been some substantial changes to the code since. I've also discovered problems with using HttpKeepAlives with my AUTD mechanism. I will let you know how this goes. If you have any ideas on this in the mean time please let me know,

Many Thanks.

NozFx