@miconda
Changing 'valueint' to 'valuedouble' need because 'valueint' has 'int' type and 'methods' are sometimes not fit into them when we obtain json message. But it fits in 'valuedouble' which has type 'double' and also been set on parse.

Situation: when client supports all methods we got right sended value '4294967295' (max unsigned int), while receiving we a convert it to 'int' (valueint) and got in debug '2147483647' (got max int) and it's wrong. In more details after that 'methods' is been set to '-2147483647' and in fact we see in supported 'methods':
1111111111111111111111111111111110000000000000000000000000000000
instead of expected
1111111111111111111111111111111111111111111111111111111111111111
and client can't operate without re-reg and setting rigth 'methods' flags.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.