Sample code for 30+ languages & platforms
Visual Basic 6.0

ReceiveString Returns Only the Immediately Available Data

See more Socket/SSL/TLS Examples

Demonstrates that Socket.ReceiveString returns only the text immediately available and not the entire response. The example connects to chilkatsoft.com over TLS and requests big_helloWorld.txt, a large text file of roughly 74,000 lines. A single ReceiveString call returns just the first portion of the response, and the example reports how many characters were received compared with the total size given by the response Content-Length header.

Background. Because ReceiveString returns whatever text is currently available, one call cannot indicate whether the full response has arrived. Knowing when a response is complete requires either a known expected length (such as a Content-Length header or an application-defined length prefix), receiving in a loop until that many bytes are collected, or receiving until the peer closes the connection. This example sends a minimal HTTP request only to exercise ReceiveString against a public server; for actual HTTP work, use the Chilkat Http, Rest, or HttpCurl classes.

Chilkat Visual Basic 6.0 Downloads

Visual Basic 6.0
Dim success As Long
success = 0

Dim socket As New ChilkatSocket

'  Connect to chilkatsoft.com over TLS.
Dim bTls As Long
bTls = 1
Dim maxWaitMs As Long
maxWaitMs = 5000
success = socket.Connect("chilkatsoft.com",443,bTls,maxWaitMs)
If (success = 0) Then
    Debug.Print socket.LastErrorText
    Exit Sub
End If

socket.StringCharset = "utf-8"

'  Send an HTTP GET request for big_helloWorld.txt, a large text file of roughly 74,000 lines of
'  "Hello World!".  This uses a minimal HTTP request only to exercise ReceiveString against a public
'  server -- for real HTTP work, use the Chilkat Http, Rest, or HttpCurl classes instead.
Dim httpReq As String
httpReq = "GET /big_helloWorld.txt HTTP/1.1" & vbCrLf & "Host: chilkatsoft.com" & vbCrLf & "Connection: close" & vbCrLf & vbCrLf
success = socket.SendString(httpReq)
If (success = 0) Then
    Debug.Print socket.LastErrorText
    Exit Sub
End If

'  Call ReceiveString a single time.  It returns only the text that is immediately available --
'  typically just the first network packet -- and does NOT wait for the entire response to arrive.
Dim responseText As String
responseText = socket.ReceiveString()
If (socket.LastMethodSuccess = 0) Then
    Debug.Print socket.LastErrorText
    Exit Sub
End If

'  Load the received text into a StringBuilder so its length can be measured and the Content-Length
'  header extracted.  The Content-Length header gives the total size, in bytes, of the response body.
Dim sb As New ChilkatStringBuilder
success = sb.Append(responseText)
Dim contentLength As String
contentLength = sb.GetBetween("Content-Length: ",vbCrLf)
If (sb.LastMethodSuccess = 0) Then
    Debug.Print sb.LastErrorText
    Exit Sub
End If

'  Compare what this single ReceiveString returned against the full size of the expected response.
'  The received amount is only a small fraction of the total.
Debug.Print "Characters received so far (headers + partial body): " & sb.Length
Debug.Print "Expected response body size (Content-Length): " & contentLength & " bytes"

'  A single ReceiveString call returns whatever is currently available, so it cannot indicate whether
'  the full response has arrived.  This makes it difficult to know when a response is complete: the
'  application must either know how many bytes to expect (for example from a Content-Length header or
'  an application-defined length prefix) and keep receiving until that many bytes are collected, or
'  keep receiving until the peer closes the connection.