Closed boks1971 closed 2 months ago
Latest commit: 0dbbb848c8a7f18e3b538528d15970de19ecee1f
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@lukasIO I was thinking of making the simulation option just a
LeaveRequest
. And when simulating, client side can just setAction
field ofLeaveRequest
. But, decided against it as I did not see the use case for it and also wanted to keep it simple/specific.Let me know if I should change that to a generic
LeaveRequest
. If doing genericLeaveRequest
, server behaviour would beAction = DISCONNECT
: server will close the participant and send aLeaveRequest
withAction = DISCONNECT
.Action = RESUME
, server will sendLeaveRequest
withAction = RESUME
and it will not include self region inRegionSettings
.Action = RECONNECT
, server will sendLeaveRequest
withAction = RECONNECT
and it will not include self region inRegionSettings
.As the current simulation is only for full reconnect, it will behave like
#3
above.Also, this option will be supported only in cloud.
Please let me know if I should change this or just leave it as a boolean.