(Android™) curl How Known Variables Reduce Execution Steps

See more CURL Examples

This example demonstrates how previously resolved values can simplify future executions.

When DoYourThing is called for a curl command, it builds an execution plan by resolving any missing inputs. This may require running one or more helper curl commands to produce the needed values.

As each command runs, any defined output variables are stored in the HttpCurl object and remain available for subsequent calls.

If another curl command is executed afterward—and it requires variables that are already known from earlier executions—those inputs do not need to be resolved again. As a result, the dependency chain is shorter, and the execution plan contains fewer steps.

In other words, each call to DoYourThing benefits from the current set of known variables. The more values that have already been resolved, the simpler and more direct the execution plan becomes.

This demonstrates that dependency resolution is dynamic and incremental: only missing inputs trigger additional steps, while previously computed values are reused automatically.

Note: This example requires Chilkat v11.5.0 or greater.

For more information, see https://www.chilkatsoft.com/curl_dependency_engine.asp

Chilkat Android™ Downloads Android™ Java Libraries Android C/C++ Libraries

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    boolean success = false;

    success = false;

    // -----------------------------------------------------------------------------
    // NOTE:
    // This example builds on the earlier multi-step dependency example, where the
    // execution plan required multiple curl commands (getSite → getDrives → target).
    // 
    // If you have not seen that example, refer to it here: curl Multi-Step Dependency
    // 
    // 
    // In this example, we demonstrate how previously resolved variables (site_id,
    // drive_id, etc.) are reused across multiple calls to DoYourThing, resulting
    // in simpler execution plans for subsequent requests.
    // -----------------------------------------------------------------------------

    CkHttpCurl httpCurl = new CkHttpCurl();

    // The final curl command we want to execute.
    // It depends on {{drive_id}}, which may or may not already be known.
    String targetCurl = "curl -X GET https://graph.microsoft.com/v1.0/drives/{{drive_id}}/root/children";

    // Define helper function to get drives (produces drive_id, requires site_id)
    String fnName = "getDrives";
    httpCurl.AddFunction(fnName,"curl -X GET https://graph.microsoft.com/v1.0/sites/{{site_id}}/drives");
    String jsonPath = "value[0].id";
    httpCurl.AddOutput(fnName,jsonPath,"drive_id");

    // Define helper function to get site (produces site_id, requires site_name)
    fnName = "getSite";
    httpCurl.AddFunction(fnName,"GET https://graph.microsoft.com/v1.0/sites/root:/sites/{{site_name}}");
    jsonPath = "id";
    httpCurl.AddOutput(fnName,jsonPath,"site_id");

    // Provide the initial known input.
    httpCurl.SetVar("site_name","test");

    // Configure OAuth2 authentication (client credentials with secrets)
    CkJsonObject jsonOAuth2 = new CkJsonObject();
    jsonOAuth2.put_EnableSecrets(true);
    jsonOAuth2.UpdateString("oauth2.client_id","!!sharepoint|oauth2|client_id");
    jsonOAuth2.UpdateString("oauth2.client_secret","!!sharepoint|oauth2|client_secret");
    jsonOAuth2.UpdateString("oauth2.scope","https://graph.microsoft.com/.default");
    jsonOAuth2.UpdateString("oauth2.token_endpoint","!!sharepoint|oauth2|token_endpoint");
    httpCurl.SetAuth(jsonOAuth2);

    // -----------------------------------------------------------------------------
    // EXAMINE THE EXECUTION PLAN (BEFORE RUNNING):
    // At this point, drive_id and site_id are NOT known.
    // We can inspect the plan that will be executed without sending any requests.
    // -----------------------------------------------------------------------------
    String executionPlan = httpCurl.examinePlan(targetCurl);
    Log.i(TAG, "Execution plan before first call:");
    Log.i(TAG, executionPlan);

    // Expected output:
    // 
    // Plan for targetCurl(drive_id)
    // 1) site_id = getSite(site_name)
    // 2) drive_id = getDrives(site_id)
    // 3) targetCurl(drive_id)

    // -----------------------------------------------------------------------------
    // FIRST CALL:
    // At this point, drive_id and site_id are NOT known.
    // The execution plan will include all required steps:
    // 
    //   1) getSite    → produces site_id
    //   2) getDrives  → produces drive_id
    //   3) targetCurl → uses drive_id
    // -----------------------------------------------------------------------------
    success = httpCurl.DoYourThing(targetCurl);
    if (success == false) {
        Log.i(TAG, httpCurl.lastErrorText());
        return;
        }

    Log.i(TAG, "First call completed.");
    Log.i(TAG, "site_id  = " + httpCurl.getVar("site_id"));
    Log.i(TAG, "drive_id = " + httpCurl.getVar("drive_id"));

    // -----------------------------------------------------------------------------
    // SECOND CALL (DIFFERENT TARGET):
    // Now that site_id is already known, we can run another curl command that
    // depends only on site_id. No need to call getSite again.
    // 
    // Execution plan:
    // 
    //   1) targetCurl2 → uses existing site_id
    // -----------------------------------------------------------------------------

    String targetCurl2 = "curl -X GET https://graph.microsoft.com/v1.0/sites/{{site_id}}";

    executionPlan = httpCurl.examinePlan(targetCurl2);
    Log.i(TAG, "");
    Log.i(TAG, executionPlan);

    // Expected output:
    // 
    // Plan for targetCurl(site_id)
    // 1) targetCurl(site_id)

    success = httpCurl.DoYourThing(targetCurl);
    if (success == false) {
        Log.i(TAG, httpCurl.lastErrorText());
        return;
        }

    Log.i(TAG, "Second call completed (used existing site_id).");

    // -----------------------------------------------------------------------------
    // THIRD CALL (ORIGINAL TARGET AGAIN):
    // drive_id is already known from the first call.
    // Therefore, no helper functions are needed this time.
    // 
    // Execution plan:
    // 
    //   1) targetCurl → uses existing drive_id
    // -----------------------------------------------------------------------------
    executionPlan = httpCurl.examinePlan(targetCurl);
    Log.i(TAG, "");
    Log.i(TAG, executionPlan);

    // Expected output:
    // 
    // Plan for targetCurl(drive_id)
    // 1) targetCurl(drive_id)

    success = httpCurl.DoYourThing(targetCurl);
    if (success == false) {
        Log.i(TAG, httpCurl.lastErrorText());
        return;
        }

    Log.i(TAG, "Third call completed.");
    Log.i(TAG, "No dependency resolution was needed because all inputs were already known.");

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}