View Single Post
Posts: 57 | Thanked: 96 times | Joined on Jul 2012
#5150
Originally Posted by Scorpius View Post
That's the time in milliseconds when Yappari will try another read from the network socket.

If you change it to a higher value, the GUI should freeze more often in bad connections. If you change it to a lower value, the GUI should response better, but your battery will last a lot less.

It doesn't really has anything to do with the socket timeout, which is 300 seconds (5 minutes).

If you read the code you'll see that no matter what value you set there, it's inside a while loop so it will still try to read until it reads what it needs to read, or until the socket times out and throws an exception.
Yes it is. I feel the freeze sometime just like in version 1.1.46.
But I think I can live with that.
Because if it is set to 1000, I can't connect at all when on 2.5G.
It says connecting, then connected, and then timeout.
It's keep on looping like that without really connected.

So far, 3000 will make yappari connected normally without time out.
I'm still unsure because I haven't really read all the code and how it worked, but really thank you for your explanation.
 

The Following 2 Users Say Thank You to Zero Six For This Useful Post: