quote:
Originally posted by CookieRevised
Yeah, didn't think of that.... although it would only happen when the integer is 0, because text like that is unicode and thus each character is read in pairs of two bytes. So in the pair of 0x45 0x00, the 0x00 isn't an end of string marker. The end of string marker in unicode consists of a 0 word (integer value 0), not a 0 byte. Or so it should be... didn't tested this though...
true, but i said that because i wasn't sure about if the messages are sent as unicode (16 bits NUL terminator) or as ascii (usual 8 bits NUL)
quote:
Originally posted by CookieRevised
yup, or the first method I mentioned. Well, actually those two are the same, you both send the numbers/digits as literal characters. But with the hexadecimal style you could send more integers at once...
(thinking of it, you could make your base 36 and use all the letters of the alphabeth and thus sending even more integers... or even an higher base using other ascii characters )
i thought in that (base 36 or more) but i don't think it's worth it... only for a very few integers you would be able to send less characters than using hexadecimal
/ 
