Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider adding another notification ordering requirement #259

Closed
d-gregorczyk opened this issue Feb 15, 2024 · 1 comment · Fixed by #277
Closed

Consider adding another notification ordering requirement #259

d-gregorczyk opened this issue Feb 15, 2024 · 1 comment · Fixed by #277
Assignees
@d-gregorczyk
Labels
Release Candidate Issue is being considered for the next release Spec An proposal related to the content or organization of the specification
Milestone
SDPi 1.3 Review

Comments

@d-gregorczyk
Copy link
Collaborator

There are a couple of requirments that are supposed to control the delivery of reports in the same order they are send. However, this does not account for OperationInvokedReports. I therefore suggest to add a requirement that explicity ask for only sending a notification when there is not another transmission pending:

A SOMDS Provider shall not send a notification of a subscription as long as there is another notification pending for that subscription.
@d-gregorczyk d-gregorczyk added the Comment NEW A submitted comment waiting to be reviewed and dispositioned label Feb 15, 2024
@ToddCooper ToddCooper added Spec An proposal related to the content or organization of the specification Release Candidate Issue is being considered for the next release and removed Comment NEW A submitted comment waiting to be reviewed and dispositioned labels Feb 16, 2024
@ToddCooper ToddCooper added this to the SDPi 1.3 Review milestone Feb 16, 2024
@ToddCooper
Copy link
Collaborator

SDPi Friday 2024.02.16: This new requirement block would end up in TF-2A with related requirements.

d-gregorczyk added a commit that referenced this issue Mar 8, 2024
@d-gregorczyk
#259 Add requirement to enforce serialization of any notifications.
96be94c
@d-gregorczyk d-gregorczyk linked a pull request Mar 8, 2024 that will close this issue
#259 Add requirement to enforce serialization of any notifications. #277
Merged
2 tasks
ToddCooper pushed a commit that referenced this issue Mar 8, 2024
@d-gregorczyk
#259 Add requirement to enforce serialization of any notifications. (#…
d75b9ee 
…277)
@github-project-automation github-project-automation bot moved this from New issues to Done in Gemini SDPi Releases Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@d-gregorczyk d-gregorczyk

Labels
Release Candidate Issue is being considered for the next release Spec An proposal related to the content or organization of the specification
Projects
Gemini SDPi Releases
Archived in project
Milestone
SDPi 1.3 Review
Development

Successfully merging a pull request may close this issue.

#259 Add requirement to enforce serialization of any notifications. IHE/DEV.SDPi
2 participants
@ToddCooper @d-gregorczyk