I did some testing on my own. I learned a little bit, but I'm not sure what.
I modified the server to send the text in a loop
i number of times, and to do so with a delay of
j ms, implemented with
sleep, j. I modified the gui so that I could specify both
i and
j. I tested with client and server running on the same computer.
The send code is very simple and is shown below. I did not implement an FD_WRITE event, hoping to prove send() would fail if called in a loop too quickly. I thought for sure I'd receive a WSAEWOULDBLOCK error if the loop was too quick.
Code:
Loop % Repeat
{
sendret := DllCall("Ws2_32\send", "UInt", socket, "Str", SendData, "Int", SendDatasize, "Int", 0)
WinsockError := DllCall("Ws2_32\WSAGetLastError")
if WinsockError <> 0
MsgBox % "send() indicated Winsock error " . WinsockError
sleep,Delay
}
I added Critical to the first line of the client's ReceiveData routine so it couldn't be interrupted, and modified the receive loop to loop on recv() until there was no data left, and
then process it. The code is as follows:
Code:
ReceiveData(wParam, lParam)
; By means of OnMessage(), this function has been set up to be called automatically whenever new data
; arrives on the connection.
{
Critical
global ShowReceived
global MyEdit
global LinesReceived
Data=
socket := wParam
ReceivedDataSize = 4096 ; Large in case a lot of data gets buffered due to delay in processing previous data.
Loop ; This loop solves the issue of the notification message being discarded due to thread-already-running.
{
VarSetCapacity(ReceivedData, ReceivedDataSize, 0) ; 0 for last param terminates string for use with recv().
ReceivedDataLength := DllCall("Ws2_32\recv", "UInt", socket, "Str", ReceivedData, "Int", ReceivedDataSize, "Int", 0)
if ReceivedDataLength = 0 ; The connection was gracefully closed,
ExitApp ; The OnExit routine will call WSACleanup() for us.
if ReceivedDataLength = -1
{
WinsockError := DllCall("Ws2_32\WSAGetLastError")
if ( WinsockError = 10035 ) { ; WSAEWOULDBLOCK, which means "no more data to be read".
break
}
if WinsockError <> 10054 ; WSAECONNRESET, which happens when Network closes via system shutdown/logoff.
; Since it's an unexpected error, report it. Also exit to avoid infinite loop.
MsgBox % "recv() indicated Winsock error " . WinsockError
ExitApp ; The OnExit routine will call WSACleanup() for us.
}
Data .= ReceivedData
}
; process the data received.
Loop, parse, Data, `n, `r
{
LinesReceived++
if (LinesReceived = 1) {
ShowReceived = %LinesReceived%: %A_LoopField%
} else {
ShowReceived = %ShowReceived%`n%LinesReceived%: %A_LoopField%
}
;Tooltip % ShowReceived
GuiControl,, MyEdit, %ShowReceived%
}
return 1 ; Tell the program that no further processing of this message is needed.
}
With a repeat of 5 and a delay of 1ms I still received all messages on the client. With a delay of 0 ms the client would usually receive 3 out of 5, though at times the text of 2 messages would be part of one receive on the client end. If I commented out the sleep command altogether, the client would receive just 1 message.
Neither send() or recv() ever return an error status. The fact that some data is being lost but no error status returned tells me there's a coding mistake somewhere, but I don't know where it is.
Login
Register
FAQ
Search
vPhiLho 