Android socket pushed frequently cause caton page-CodePudding

Ask bosses Android socket pushed frequently cause caton because UI page frequently apply colours to a drawing or something? How to solve? Urgent urgent ~ ~ ~

CodePudding user response:

The frequent operation of movement in the thread processing

CodePudding user response:

reference 1st floor usecf response:

to the action of frequent operation in the thread processing

it because frequent push or frequent rendering

CodePudding user response:

Frequent rendering is more frequent?
In my opinion, the big probability is lead to render the page in your main thread and the card,,
Check code or post code, under the analysis together

CodePudding user response:

The

reference dear Joe reply: 3/f

frequent rendering is more frequent?
In my opinion, the big probability is lead to render the page in your main thread and the card,,
Check code or post code, together with analysis of

is frequent delivery is no problem, the problem is to render data?

CodePudding user response:

reference 4 floor xxs5258 response:

Quote: reference dear Joe reply: 3/f
frequent rendering is more frequent?
In my opinion, the big probability is lead to render the page in your main thread and the card,,
Check code or post code, together with analysis of

is frequent delivery is no problem, the problem is to render data?

is similar to a second push a few hundred, is everyone in the room click will be pushed to everyone in the room phone, mainly to do real-time

CodePudding user response:

Frequent time-consuming operation in the child thread

CodePudding user response:

Does each push updates page data, page updates too frequently will cause caton, decrease the refresh rate, or add a lock

CodePudding user response:

Socket message delivery, this should not be in the UI thread to handle the message, it is recommended to use the child thread processing

CodePudding user response:

refer to the eighth floor IT_ bear response:

socket message delivery, this should not be in the UI thread to handle the message, it is recommended to use the child thread processing

is in the child thread processing, push after dozens of don't push

CodePudding user response:

The child thread push + receive this not card ah ~
UI data refresh, more, ah,
If notice is, this is not the card
If the page lists the card?

CodePudding user response:

The

references to the tenth floor Krisez response:

child thread push + receive this not card ah ~
UI data refresh, more, ah,
If notice is, this is not the card
If the page lists the card?

hello, that how the UI list card, how to solve

CodePudding user response:

11 references xxs5258 response:

Quote: reference to the tenth floor Krisez response:

The child thread push + receive this not card ah ~
UI data refresh, more, ah,
If notice is, this is not the card
If the page lists the card?

hello, that how the UI list card, how to solve

The refresh fast
1, you add a Boolean value as a switch, or lock
2, do a delay processing, no news is the 1 s or within 0.5 s is returned to the UI, if any, are assembled into a list, is to a message, such as 0.5 1 s, the last of the refresh time is, push after receiving time 1-2 s, 1.5 3 s waiting time, almost in real time, or even shorter)
3, make a list of the initiative to get the data, not passive (listen to the data change is automatically refresh)
The list to refresh

CodePudding user response:

refer to 12 floor Krisez reply:

Quote: reference 11 floor xxs5258 response:

The
Quote: reference to the tenth floor Krisez response:

The child thread push + receive this not card ah ~
UI data refresh, more, ah,
If notice is, this is not the card
If the page lists the card?

hello, that how the UI list card, how to solve

The refresh fast
1, you add a Boolean value as a switch, or lock
2, do a delay processing, no news is the 1 s or within 0.5 s is returned to the UI, if any, are assembled into a list, is to a message, such as 0.5 1 s, the last of the refresh time is, push after receiving time 1-2 s, 1.5 3 s waiting time, almost in real time, or even shorter)
3, make a list of the initiative to get the data, not passive (listen to the data change is automatically refresh)
List again refresh

ok, thank you