chjk Member Licensed User Longtime User Nov 21, 2015 #1 AsyncStreams+Socket send string exist garbage data! How to solve it? Attachments src.JPG 13.6 KB · Views: 574 dataError.JPG 8.3 KB · Views: 621
JanPRO Well-Known Member Licensed User Longtime User Nov 21, 2015 #2 By default, Indy uses 7bit ASCII as its character encoding Click to expand... http://stackoverflow.com/questions/27609332/indy-10-tidtcpserver-encoding-characters Upvote 0
By default, Indy uses 7bit ASCII as its character encoding Click to expand... http://stackoverflow.com/questions/27609332/indy-10-tidtcpserver-encoding-characters
Erel B4X founder Staff member Licensed User Longtime User Nov 22, 2015 #3 Make sure not to initialize it in prefix mode. Upvote 0
chjk Member Licensed User Longtime User Nov 22, 2015 #4 Erel said: Make sure not to initialize it in prefix mode. Click to expand... Thanks, Indeed prefix mode! my initialize code AStreams.InitializePrefix(sc.InputStream, False, sc.OutputStream, "AStreams") but in b4a this code not this problem! now b4i initialize code change AStreams.Initialize(sc.InputStream, sc.OutputStream, "AStreams") Solved it! Upvote 0
Erel said: Make sure not to initialize it in prefix mode. Click to expand... Thanks, Indeed prefix mode! my initialize code AStreams.InitializePrefix(sc.InputStream, False, sc.OutputStream, "AStreams") but in b4a this code not this problem! now b4i initialize code change AStreams.Initialize(sc.InputStream, sc.OutputStream, "AStreams") Solved it!
Erel B4X founder Staff member Licensed User Longtime User Nov 23, 2015 #5 There is no difference between B4A and B4i. You can only use prefix mode if both sides of the connection adhere to the "prefix" protocol. Upvote 0
There is no difference between B4A and B4i. You can only use prefix mode if both sides of the connection adhere to the "prefix" protocol.
