For ClientRequestOpSpecTimeout, MaxNumInventoryParameterSpecsPerAISpec, MaxNumAccessSpecs, and MaxNumOpSpecsPerAccessSpec, the 0 means that there are an unlimited number of those things supported. For the MaxPriorityLevelSupported, a 0 means that no priority is suppoted.
Currently our reader is built to support more than one ROSpec (i.e. the data structures are in place), but that functionality has not been tested. So there are no specific plans, but hopefully all it would require would be some testing and fleshing out of minor bugs. -Kyle Ruibin Zhou wrote: > > Kyle, > > These are some major LLRP capabilities based on the > GET_READER_CAPABILITIES_RESPONSE from Rifidi: > > LLRPCapabilities: > CanDoRFSurvey: false > CanReportBufferFillWarning: false > SupportsClientRequestOpSpec: false > CanDoTagInventoryStateAwareSingulation: false > SupportsEventAndReportHolding: false > MaxPriorityLevelSupported: 0 > ClientRequestOpSpecTimeout: 0 > *MaxNumROSpecs*: 1 > MaxNumSpecsPerROSpec: 1 > MaxNumInventoryParameterSpecsperAISpec: 0 > *MaxNumAccessSpecs*: 0 > MaxNumOpSpecsPerAccessSpec: 0 > > > For those capabilities with value "0", such as MaxNumAccessSpecs, does > it mean it is unlimited? Currently the MaxNumROSpecs is "1", is there > plan for Rifidi to support multiple ROSpecs? > > > Thanks. > > > > Ruibin Zhou > > RFID DataCapture Development > IBM RTP > [EMAIL PROTECTED] > 919-543-1221 T/L: 441-1221 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Rifidi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rifidi-developers
