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

Change duration of an active session #220

Closed
emil-cheung opened this issue Sep 12, 2023 · 2 comments · Fixed by #216
Closed

Change duration of an active session #220

emil-cheung opened this issue Sep 12, 2023 · 2 comments · Fixed by #216
Assignees
Labels
enhancement New feature or request

Comments

@emil-cheung
Copy link
Collaborator

Problem description
Currently there is no mean to change the duration of an active session. However, there are use cases require extending the duration. A dedicated endpoint is proposed for this operation.

Possible evolution
N/A

Alternative solution
Use PATCH operation to change the duration.

Additional context
Originally, PATCH operation was proposed to change the duration. However, according the further discussion in issue #47 , a dedicated endpoint is preferred since it is straightforward to developers. This new issue is created to reflect the community discussion.

@emil-cheung emil-cheung added the enhancement New feature or request label Sep 12, 2023
@ShutingQing
Copy link

Hi emil, how about discuss here Include support for /PATCH sessions? There will be more history infos.

@hdamker
Copy link
Collaborator

hdamker commented Sep 19, 2023

@ShutingQing

Hi emil, how about discuss here Include support for /PATCH sessions? There will be more history infos.

You are right, it is important to link back to the discussion in issue #47. The course of discussion there reduced the scope of a potential /PATCH operation step by step and ended with the conclusions:

  • Duration can't be "patched" but should be an explicit endpoint (this issue here)
  • NotificationAuthToken ... discussion postponed until new Event/Notification structure clarified (hopefully including handling of security)

All other points were already postponed earlier, incl. QoSProfile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants