search

pnp-software / cordetfw

C Implementation of a Software Framework for Service-Oriented Applications with PUS Support
Mozilla Public License 2.0
13 stars 1 forks source link

Destination of Event Reports #113

Closed pasetti closed 5 years ago

pasetti commented 6 years ago

We should consider making the destination of event report the same as the source of the command which enables them.

SergeValera commented 6 years ago

Please, acknowledge that the Standard requirement 6.5.4b states: "The destination of the event reports generated by an event reporting subservice shall be declared when specifying that subservice".

pasetti commented 6 years ago

Our current statement of compliance to requirement 6.5.4b (see appendix D of our PUS Extension Document simply leaves the declaration of the destination of an event report to an application, In this ticket we are proposing to change this policy and use an automatic mechanism whereby the destination of an event report is the same as the source of the last command which enabled that report.

The question is: would such a rule violate clause 6.5.4b? In my view, there is no violation because we are declaring the destination of an event report implicitly by defining the rule through which that destination is determined.

pasetti commented 6 years ago

I have defined the destination of event reports as follows: "An initial destination is pre-defined. At run-time, the destination is the same as the source of the most recent command which enabled the event report". The implementation must be adapted.

pasetti commented 5 years ago

Upon reflection, it probably makes more sense to stick to the literal interpretation of clause 6.5.4b and to have fixed and statically defined destinations for all event reports. I will update the specification of the PUS Extension accordingly.

pasetti commented 5 years ago

Update has been made in release 0.2 of the PUS Extension Specification.