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.

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

Updated the spec so that it reflects the behaviour implemented in ably-cocoa PR #1847 #181

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

maratal
Copy link
Collaborator

@maratal maratal commented Feb 4, 2024

Updated the spec so that it reflects the behaviour implemented in ably/ably-cocoa#1847, where a new device ID is generated as soon as the previous ones are cleared, so that id is never null.

Originally posted by @lawrence-forooghian here

Closes #180

@@ -1207,7 +1207,7 @@ h3(#activation-state-machine). Activation State Machine
*** @(RSH3g1)@ On event @CalledDeactivate@:
**** @(RSH3g1a)@ Transitions to @WaitingForDeregistration@.
*** @(RSH3g2)@ On event @Deregistered@:
**** @(RSH3g2a)@ Clears all local @DeviceDetails@.
**** @(RSH3g2a)@ Generates a new pair of device @id@ and @deviceSecret@ as described in "RSH3a2b":#RSH3a2b. Clears all other local @DeviceDetails@.
Copy link
Collaborator

Choose a reason for hiding this comment

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

This only partially describes the ably-cocoa behaviour, doesn't it? In ably-cocoa, id and deviceSecret generation are completely decoupled from the CalledActivate event, meaning that RSH3a2b and RSH8b would also need to be changed if we wished for the spec to describe the behaviour of ably-cocoa.

Also, same point as #182 (comment) re spec point modification.

@SimonWoolf
Copy link
Member

I'm not really familiar with the context here or the push activation state machine implemented in sdks, so going to untag myself and suggest @owenpearson instead

@SimonWoolf SimonWoolf requested review from owenpearson and removed request for SimonWoolf February 12, 2024 20:35
…y/ably-cocoa#1847, where a new device ID is generated as soon as the previous ones are cleared, so that id is never null.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

DeviceDetails.id (PCD2) should be nullable.
3 participants