My app already keeps track of network state (currently I'm only using WiFi)
- if I have no connectivity, I abort the long poll so the wireless radio
interface should not be an issue.
I've alteady tested 'network out of range' issues quite extensively since
my app is being deployed in environments
mmm it might be useful to dump the radio logs
On 9 April 2013 15:26, Stephan Steiner wrote:
> I think I may have used the wrong title thus giving the wrong impression of
> what the problem is or isn't.
>
> I already have
>
> System.Net.ServicePointManager.DefaultConnectionLimit = 4;
>
> In my c
I think I may have used the wrong title thus giving the wrong impression of
what the problem is or isn't.
I already have
System.Net.ServicePointManager.DefaultConnectionLimit = 4;
In my code - I've had this problem earlier (both of you participated in the
thread last year), and if this were it,
Correct. you probably want to change the defaults
System.Net.ServicePointManager.DefaultConnectionLimit = 4;
On 6 April 2013 00:12, Sayed Arian Kooshesh wrote:
> sounds like a problem with servicepointmanager. IT limits your connections
> to a site to 2 and can cause a limitation in your conne
sounds like a problem with servicepointmanager. IT limits your connections
to a site to 2 and can cause a limitation in your connections. You might
want to look into it.. just a fly by guess.
http://msdn.microsoft.com/en-us/library/system.net.servicepointmanager.aspx
On Fri, Apr 5, 2013 at 3:42
Hi
I'm using long polling in my app and I recently noted something funny - it
seems there quite a low threshold for how long the server may take to
respond. It generally tends to work just fine with a 10 minute timeout, but
recently more and more the server side timeout runs out so the server
resp
