Hi Vicente,
sorry! I haven't noticed that.
I guess that this has something to do with String encoding in Java.
The Jabaco framework takes Winsock data as Strings, not as arrays of bytes.
If your are using the following DataArrival handler, you see what bytes arrive:
|
Jabaco Source
|
1
2
3
4
5
6
7
8
9
10
11
12
13
|
Private Sub tcpServer_DataArrival(ByVal bytesTotal As Long)
Dim l As Long
Dim i As Integer
Dim s As java#lang#String = tcpServer.GetData()
Text3.Text = Text3.Text & vbCrLf & bytesTotal & " bytes: " & vbCrLf
For l = 0 To bytesTotal - 1
i = s.charAt(l)
Text3.Text= Text3.Text & l & ": " & Chr$(i) & " " & CStr(i) & vbCrLf
Next l
End Sub
|
The "63" is just a question mark "?" indicating that a given byte value is no valid character for String encoding "ISO-8859-1".
ISO-8859-1 is the character encoding used internally for the Chr() function.
Greetings
A1880