Add new subrequest related functions

src/vmod_zipflow.c

@@ -108,6 +108,33 @@ get_zipflow_task(VRT_CTX)
  * VCL interface
  */
 
+VCL_VOID
+vmod_subreq(VRT_CTX, VCL_STRING url)
+{
+	CHECK_OBJ_NOTNULL(ctx, VRT_CTX_MAGIC);
+
+	// XXX TODO
+	(void) url;
+}
+
+VCL_BOOL
+vmod_is_subreq(VRT_CTX)
+{
+	CHECK_OBJ_NOTNULL(ctx, VRT_CTX_MAGIC);
+
+	// XXX TODO
+	return (1);
+}
+
+VCL_VOID
+vmod_bundle(VRT_CTX, VCL_BOOL toggle)
+{
+	CHECK_OBJ_NOTNULL(ctx, VRT_CTX_MAGIC);
+
+	// XXX TODO
+	(void) toggle;
+}
+
 VCL_VOID
 vmod_set_level(VRT_CTX, VCL_INT level)
 {

src/vmod_zipflow.vcc

@@ -37,6 +37,26 @@ Example
 		set resp.filters += " zipflow";
 	}
 
+$Function VOID subreq(STRING url)
+
+Issue a sub requets to *url* when the VDP runs, similar to ESI
+processing.
+
+This function can be called any number of times. The sub request can
+be identified using `zipflow.is_subreq()`_. In the sub request,
+`zipflow.set_level()`_ and `zipflow.meta()`_ should be used to control
+how zipflow handles the body.
+
+$Function BOOL is_subreq()
+
+True if the current request is a zipflow sub request.
+
+$Function VOID bundle(BOOL)
+
+By default, any content handled by zipflow, be it in the parent or sub
+reuqest, is bundled in the resulting ZIP file. This function can be
+used to diable or re-enable bundling of the request's body.
+
 $Function VOID set_level(INT level)
 
 $Restrict vcl_init client backend