Re: [Digir-dev] maxInventoryResponseRecords

[Dave V. <vie...@ku...>]

Hi Donald,
you have correctly surmised that the mechanism for paging is to include 
a filter for greater than the last value returned in the inventory 
response.  The only annoyance with this is that the reponse must be 
parsed to determine what that last value is.

If there is sufficient demand, then the protocol could be modified 
slightly to include a start and count record number as is currently 
defined for the search request message.  Another option is to set 
maxInventoryResponseRecords to a very large value.

Since changing the inventory request message is an alteration to the 
protocol, it would be good to get feedback on a change to support paging 
by inventory record number.  In effect the change would alter an 
inventory request message from something like:

...
   <inventory>
     [<filter>...</filter>]
     [<count>true | false</count>]
     <ns:inv_me />
   </inventory>
...

to:

...
   <inventory [start="integer"] [limit="integer"]>
     [<filter>...</filter>]
     [<count>true | false</count>]
     <ns:inv_me />
   </inventory>
...

where both the start and limit attributes are optional integer values. 
Start indicates the index number of the starting inventory record in the 
response, limit indicates the maximum number of inventory records in the 
response.

It's a fairly harmless change from the provider's point of view.

regards,
   Dave V.

dh...@gb... wrote:

> The PHP provider configuration file for a resource offers the opportunity
> to limit the number of records returned for a search request and for an
> inventory request (maxSearchResponseRecords and
> maxInventoryResponseRecords).
> 
> In the case of a search request a user can page through the response
> records to retreive those beyond this limit by using the limit and start
> attributes of the record element.  However the inventory request does not
> include any such options.  How is a user expected to retrieve the
> additional elements when the inventory count exceeds the limit?  (I have
> tried adding an extra start=1001 parameter in the URL but that doesn't
> seem to get through.)
> 
> The only means to do this at the moment would seem to be to include a
> filter for records which are greater than the value returned in the last
> record on the previous inventory requets (since I think the results of an
> inventory are always sorted).
> 
> Shouldn't the digir schema include the appropriate attributes in one of
> the inventory request elements?  Or is there some better way to do this?
> 
> Thanks,
> 
> Donald
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> DiGIR-developers mailing list
> DiG...@li...
> https://lists.sourceforge.net/lists/listinfo/digir-developers
>