Difference between revisions of "ReadCycle Class Hierarchy"
From RifidiWiki
(→ReadCycle) |
|||
Line 2: | Line 2: | ||
[[Image:ReadCycle.png|thumb|400px]] | [[Image:ReadCycle.png|thumb|400px]] | ||
=ReadCycle= | =ReadCycle= | ||
+ | A ReadCycle represents one cycle of interaction with a sensor. It can contain 0 to many TagReadEvent objects. A cycle of interaction might entail polling the sensor for data or perhaps the sensor is pushing data to the edge server. It is also important to realize that since the Edge Server supports the concept of logical readers, a single ReadCycle might contain tag reads from multiple physical readers. | ||
+ | |||
=TagReadEvent= | =TagReadEvent= | ||
=DatacontainerEvent= | =DatacontainerEvent= | ||
=EpcGeneration1Event= | =EpcGeneration1Event= | ||
=EpcGeneration2Event= | =EpcGeneration2Event= |
Revision as of 18:30, 14 October 2009
The sensors plugins in the Sensor Abstraction Layer produce ReadCycle objects that are put into Esper. Because you query objects (rather than tables) in Esper, you need to know the class hierarchy of ReadCycle in order to write queries.
Contents
ReadCycle
A ReadCycle represents one cycle of interaction with a sensor. It can contain 0 to many TagReadEvent objects. A cycle of interaction might entail polling the sensor for data or perhaps the sensor is pushing data to the edge server. It is also important to realize that since the Edge Server supports the concept of logical readers, a single ReadCycle might contain tag reads from multiple physical readers.