GFS: scan handler gets extra_args from request
authorAdam Dickmeiss <adam@indexdata.dk>
Mon, 11 Feb 2013 14:52:38 +0000 (15:52 +0100)
committerAdam Dickmeiss <adam@indexdata.dk>
Mon, 11 Feb 2013 14:52:38 +0000 (15:52 +0100)
include/yaz/backend.h
src/seshigh.c

index 84df83b..8ae3f3f 100644 (file)
@@ -151,6 +151,7 @@ typedef struct bend_scan_rr {
     char *errstring;
     char *scanClause;   /**< CQL scan clause */
     char *setname;      /**< Scan in result set (NULL if omitted) */
+    Z_SRW_extra_arg *extra_args; /**< SRU extra request parameters (input) */
     char *extra_response_data;   /**< SRW extra XML response (output) */
 } bend_scan_rr;
 
index 08c4def..3b49190 100644 (file)
@@ -1329,6 +1329,7 @@ static void srw_bend_scan(association *assoc,
         bsrr->step_size = &step_size;
         bsrr->entries = 0;
         bsrr->setname = 0;
+        bsrr->extra_args = sr->extra_args;
         bsrr->extra_response_data = 0;
 
         if (bsrr->num_entries > 0)
@@ -3051,6 +3052,7 @@ static Z_APDU *process_scanRequest(association *assoc, request *reqb)
     bsrr->setname = yaz_oi_get_string_oid(&req->otherInfo,
                                           yaz_oid_userinfo_scan_set, 1, 0);
     bsrr->entries = 0;
+    bsrr->extra_args = 0;
     bsrr->extra_response_data = 0;
     /* For YAZ 2.0 and earlier it was the backend handler that
        initialized entries (member display_term did not exist)