ReceiveSb Returns Only the Immediately Available Data

See more Socket/SSL/TLS Examples

Demonstrates that Socket.ReceiveSb returns only the data 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 ReceiveSb 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.

#include <C_CkSocketW.h>
#include <C_CkStringBuilderW.h>

void ChilkatSample(void)
    {
    BOOL success;
    HCkSocketW socket;
    BOOL bTls;
    int maxWaitMs;
    const wchar_t *httpReq;
    HCkStringBuilderW sb;
    const wchar_t *contentLength;

    success = FALSE;

    socket = CkSocketW_Create();

    //  Connect to chilkatsoft.com over TLS.
    bTls = TRUE;
    maxWaitMs = 5000;
    success = CkSocketW_Connect(socket,L"chilkatsoft.com",443,bTls,maxWaitMs);
    if (success == FALSE) {
        wprintf(L"%s\n",CkSocketW_lastErrorText(socket));
        CkSocketW_Dispose(socket);
        return;
    }

    CkSocketW_putStringCharset(socket,L"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 ReceiveSb against a public
    //  server -- for real HTTP work, use the Chilkat Http, Rest, or HttpCurl classes instead.
    httpReq = L"GET /big_helloWorld.txt HTTP/1.1\r\nHost: chilkatsoft.com\r\nConnection: close\r\n\r\n";
    success = CkSocketW_SendString(socket,httpReq);
    if (success == FALSE) {
        wprintf(L"%s\n",CkSocketW_lastErrorText(socket));
        CkSocketW_Dispose(socket);
        return;
    }

    //  Call ReceiveSb a single time.  It returns only the bytes that are immediately available --
    //  typically just the first network packet -- and does NOT wait for the entire response to arrive.
    sb = CkStringBuilderW_Create();
    success = CkSocketW_ReceiveSb(socket,sb);
    if (success == FALSE) {
        wprintf(L"%s\n",CkSocketW_lastErrorText(socket));
        CkSocketW_Dispose(socket);
        CkStringBuilderW_Dispose(sb);
        return;
    }

    //  The response begins with HTTP headers.  The Content-Length header gives the total size, in bytes,
    //  of the response body.
    contentLength = CkStringBuilderW_getBetween(sb,L"Content-Length: ",L"\r\n");
    if (CkStringBuilderW_getLastMethodSuccess(sb) == FALSE) {
        wprintf(L"%s\n",CkStringBuilderW_lastErrorText(sb));
        CkSocketW_Dispose(socket);
        CkStringBuilderW_Dispose(sb);
        return;
    }

    //  Compare what this single ReceiveSb returned against the full size of the expected response.  The
    //  received amount is only a small fraction of the total.
    wprintf(L"Characters received so far (headers + partial body): %d\n",CkStringBuilderW_getLength(sb));
    wprintf(L"Expected response body size (Content-Length): %s bytes\n",contentLength);

    //  A single ReceiveSb 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.


    CkSocketW_Dispose(socket);
    CkStringBuilderW_Dispose(sb);

    }