Skip to content

Conversation

@jischr
Copy link
Contributor

@jischr jischr commented Apr 1, 2025

Fixes #149

This PR should be non-normative (is it?!) i've tried to better describe the default behavior when a transmitter does not support the defaulted stream delivery method.

@jischr jischr requested a review from a team as a code owner April 1, 2025 02:29
@FragLegs
Copy link
Contributor

FragLegs commented Apr 1, 2025

I believe that @atultulshi said we should not include this in the next release because it is a backwards-incompatible change: #149

@jischr jischr requested a review from FragLegs April 1, 2025 17:54
Copy link
Contributor

@iamseanodentity iamseanodentity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as discussed on the call today.

@FragLegs
Copy link
Contributor

FragLegs commented Apr 1, 2025

For anyone reading the comments - we adjusted the language so that it is fully backwards compatible and just gives a suggestion for how to respond if the Tx does not support polling.

@FragLegs FragLegs merged commit d816d0f into openid:main Apr 1, 2025
2 checks passed
appsdesh pushed a commit to appsdesh/sharedsignals that referenced this pull request Apr 2, 2025
A follow up from openid#247
@appsdesh appsdesh mentioned this pull request Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stream creation lanaguage imply that transmiter must suport the poll delivery method if delivery method is not specified

3 participants