Again some news.In order to be understanding, I'll explain again my
problem ( and my idea of why this timeout appears ).
My application contains a service witch connects a websocket ( socket
on port 80 ) and waits "push notification".
Activities needs to send some HTTP request. So I think I have to
In fact, it already happens when not in wifi, but really less often...
I'm hopeless :(
On Jan 11, 11:40 am, lou wrote:
> New info, I think the timeout is only when I'm connected with Wifi,
> not in 3G or edge !
> Is it possible ? What can I do ?
> Thanks.
>
> On Jan 7, 6:33 pm, lou wrote:
>
>
>
New info, I think the timeout is only when I'm connected with Wifi,
not in 3G or edge !
Is it possible ? What can I do ?
Thanks.
On Jan 7, 6:33 pm, lou wrote:
> Thanks for your answer,
> And yes, I've already tried to modify these parameters, but I think it
> don't change anything, even when the
Thanks for your answer,
And yes, I've already tried to modify these parameters, but I think it
don't change anything, even when the server really don't respond.
So...another idea?
On Jan 7, 6:09 pm, ivan wrote:
> Have you tried playing with the timeouts passed via the http params?
>
> HttpParams
Have you tried playing with the timeouts passed via the http params?
HttpParams httpParameters = new BasicHttpParams();
ConnManagerParams.setMaxTotalConnections(httpParameters,
inApp.gResources.getInteger(R.integer.HTTP_MaxConnCnt));
HttpConnectionParams.setConnectionTimeout(httpParameters, 2)
5 matches
Mail list logo
