Paul, I'm still kind of confused, because I didn't see anything in the spec saying that Immediate triggers should cause RoSpecs to restart once they have stopped. So that must mean that I'm not making conclusions that a reader should draw, which makes me wonder if I'm misinterpreting other parts of the spec. If you could explain this, I'd appreciate it.
Thanks, -Kyle On Thu, 2007-11-08 at 14:53 -0800, Paul Dietrich wrote: > If an ROSpec with an immediate start trigger moves to inactive, it > should restart immediately. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Kyle > Sent: Thursday, November 08, 2007 2:39 PM > To: LLRP Toolkit Development List > Subject: [ltk-d] Immediate RoSpecStart Trigger > > Hi, I have another question about the spec. This one has to do with > ROSpecStart Triggers. My understanding from the spec is that after a > rospec is enabled, it moves to the Inactive state. From here, a rospec > start condition triggers it to begin execution. After a rospec stop > condition fires, it moves back to the inactive queue waiting on another > start condition. > > With this model in mind, the only thing that can cause a rospec to > re-execute in an automatically recurring way is the Time Based Periodic > Trigger. That is what it is there for. The immediate trigger, on the > other hand, should only start the rospec once -- as soon as it is > enabled. I did not see any 'recurrence' features listed on the immediate > start trigger, as there are listed on the TimeBasePeriodic > one(PeriodicTriggerValue). In fact, I did not see much at all on how > the Immediate Trigger should be handled. Is there any "LLRP Compliant" > way to handle whether or not the ImmediateStartTrigger should cause the > RoSpec to re-execute once it has stopped? > > Thanks for your help, > Kyle Neumeier > > > ------------------------------------------------------------------------ > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > llrp-toolkit-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > llrp-toolkit-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
