Zig Requires Chilkat v11.0.0+

How to Avoid Large Strings in HTTP Responses

See more HTTP Examples

In some programming languages/environments, returning and passing large strings is problematic for both performance and other reasons (for example, with SQL Server limitations on sizes varchar variables).

One way of avoiding the need to return the actual string data, is to pass the data from one place to another via a Chilkat StringBuilder or BinData object. This example demonstrates a simple HTTP GET where the response body contains XML approximately 274K in size. The response body is loaded into the Chilkat.Xml without the XML content ever needing to leave the native code internal to Chilkat.

Zig

const std = @import("std");
const chilkat = @import("chilkat");

pub fn main(init: std.process.Init) !void {
    const alloc = init.arena.allocator();

    // This example assumes the Chilkat HTTP API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    const http = try chilkat.Http.init();
    defer http.deinit();

    const resp = try chilkat.HttpResponse.init();
    defer resp.deinit();
    http.httpNoBody("GET", "https://www.chilkatsoft.com/hamlet.xml", resp) catch {
        std.debug.print("{s}\n", .{try http.getLastErrorText(alloc)});
        return;
    };

    const sb = try chilkat.StringBuilder.init();
    defer sb.deinit();
    // Copy the response body to sb.
    try resp.getBodySb(sb);

    const xml = try chilkat.Xml.init();
    defer xml.deinit();
    // Load the XML from the sb.
    const b_auto_trim = false;
    try xml.loadSb(sb, b_auto_trim);

    std.debug.print("The response body was {d} characters in length.\n", .{sb.getLength()});
    std.debug.print("Success.\n", .{});

    // The output is:
    //
    //     The response body was 279658 characters in length.
    //     Success.
}