none
Support for multiple QueryStrings for V4 Autoconfiguration RRS feed

  • Question

  • Hello,

    I would like to ask if it's possible to specify more than one QueryString for a particular GPD feature? Something like:

     

    *Feature: MY_FEATURE { *FeatureType: PRINTER_PROPERTY *BidiQuery: MY_FEATURE { *QueryString: "\Printer.Configuration.InstalledItems001:Index" } *BidiResponse: MY_FEATURE { *ResponseType: BIDI_INT *ResponseData: ENUM_OPTION(MY_FEATURE) } *Option: OPTION_1 { *BidiValue: INT(1) } }

    *Feature: MY_FEATURE { *FeatureType: PRINTER_PROPERTY *BidiQuery: MY_FEATURE { *QueryString: "\Printer.Configuration.InstalledItems002:Index" } *BidiResponse: MY_FEATURE { *ResponseType: BIDI_INT *ResponseData: ENUM_OPTION(MY_FEATURE) } *Option: OPTION_2 { *BidiValue: INT(2) } }


    My testing here indicates that Autoconfiguration will not work if the order of the items are jumbled (e.g., OPTION_2 comes before OPTION_1, etc.)

    Thanks!

    Friday, October 4, 2013 1:16 AM

Answers

  • Hi, John:

    The OS support for GPD-based auto-configuration only supports one QueryString value for each PRINTER_PROPERTY GPD feature. This is documented on following MSDN page:

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff544978(v=vs.85).aspx

    "A *Feature construct can contain a single *BidiQuery construct, which serves as a container for a *QueryString instance. "

    We use that QueryString to query the device about the current configuration state of the particular GPD feature. So we need to have one deterministic query string to use.

    Thanks.

    Tuesday, October 8, 2013 8:31 AM