Java

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.

Java

import com.chilkatsoft.*;

public class ChilkatExample {

  static {
    try {
        System.loadLibrary("chilkat");
    } catch (UnsatisfiedLinkError e) {
      System.err.println("Native code library failed to load.\n" + e);
      System.exit(1);
    }
  }

  public static void main(String argv[])
  {
    boolean success = false;

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

    CkHttp http = new CkHttp();

    CkHttpResponse resp = new CkHttpResponse();
    success = http.HttpNoBody("GET","https://www.chilkatsoft.com/hamlet.xml",resp);
    if (success == false) {
        System.out.println(http.lastErrorText());
        return;
        }

    CkStringBuilder sb = new CkStringBuilder();
    // Copy the response body to sb.
    success = resp.GetBodySb(sb);

    CkXml xml = new CkXml();
    // Load the XML from the sb.
    boolean bAutoTrim = false;
    success = xml.LoadSb(sb,bAutoTrim);

    System.out.println("The response body was " + sb.get_Length() + " characters in length.");
    System.out.println("Success.");

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